Of course having a TomEE-7.1 which bumps the requirement to java8 is cool. And I fully support that. But right now let's please focus on shipping TomEE-7.0.5 first. Most probably 7.1 could be done almost in parallel. But we do not have endless resources. At least I don't.
LieGrue, strub > Am 19.04.2018 um 05:25 schrieb David Blevins <[email protected]>: > > >> On Apr 18, 2018, at 4:08 AM, Mark Struberg <[email protected]> wrote: >> >> There was a discussion about this a few weeks ago where we agreed to ship >> TomEE-7.0.5 and only then switch to a branch. >> >> That's the reason why we backported tons of stuff in Johnzon, OWB and >> OpenJPA. >> Just waiting for feedback whether it now works fine or if there is still >> something broken. >> >> So my suggestion is to apply this to the TomEE8 branch and wait with the >> other PR until TomEE-7.0.5 is released. > > Kicked off a proper "Status of TomEE 8" thread so we can have a full > conversation on what to do with TomEE 8. > > If people were willing to put the effort into a TomEE 7.1 in addition to > whatever is decided in that thread, would you be ok with a TomEE 7.1 as well? > > For context: I know Jean-Louis is heading off to Brazil in May to do a TomEE > talk that shows his JWT work. Ideally he's not showing a snapshot and people > could leave with something they can try. He's doing that talk again in June. > > My personal perspective is if the decision was made to release TomEE 8 now, > I'd still see value in a 7.1 release with MicroProfile as then the users > would have the choice. Some may not want to do a Java EE 7 to Java EE 8 > upgrade, but still want to enjoy some MicroProfile technologies. > > > -David > > >
