Re: TomEE Jakarta project - have we reach the limit?

> > IMO the following is the best way: > - branch 8.0.x > - make master 9.0 and rename javax -> jakarta > - branch 9.0 after everything is working fine > - working on 10.0 in master > - maintain 8.0 and 10.0 and dont maintain the 9.0 branch +1 In terms of how we handle 9.x, I think we'd want to

Re: TomEE Jakarta project - have we reach the limit?

> On Oct 5, 2021, at 1:59 AM, Thomas Andraschko > wrote: > > yep > i think we have to maintain 8.0.x anyway as its the last javax release and > we cant expect that everyone does a fast migration > > IMO the following is the best way: > - branch 8.0.x > - make master 9.0 and rename javax -> jaka

Re: TomEE Jakarta project - have we reach the limit?

Hi all, the proposed plan by Thomas sounds reasonable. +1 IMHO, 8.0.x line should definitely be continued for those not able to migrate yet, as brought up by Jean-Louis. Given the planned 8.0.9 version will compatible and work with Java 17 (LTS), that 8.0.x line should be curated for some time.

Re: TomEE Jakarta project - have we reach the limit?

Thanks for the additional thoughts Thomas. I'll wait for some more thoughts and I might create a poll and let everyone to vote on what they like. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, Oct 5, 2021 at 10:59 AM Thomas Andraschko < andraschko.tho..

Re: TomEE Jakarta project - have we reach the limit?

yep i think we have to maintain 8.0.x anyway as its the last javax release and we cant expect that everyone does a fast migration IMO the following is the best way: - branch 8.0.x - make master 9.0 and rename javax -> jakarta - branch 9.0 after everything is working fine - working on 10.0 in maste

Re: TomEE Jakarta project - have we reach the limit?

Agreed ... 1.7.x - EOL 7.0.x and 7.1.x - mostly similar so if we maintain one, we should maintain the other. But I agree that 1 actively developed version (TomEE master/TomEE 9.x) and 1 maintained version (TomEE 8.x) is good. That'd be my choice. -- Jean-Louis Monteiro http://twitter.com/jlouismo

Re: TomEE Jakarta project - have we reach the limit?

+1 I am wondering, if we still maintain 7.0.x, 7.1.x in the future (1.7.x is eol, I guess) ? Maintenance cost will rise with every additional version branch. The last releases of 7.0.x and 7.1.x are 1 year old... but this is maybe another discussion. Am Dienstag, dem 05.10.2021 um 10:05 +0200 s

Re: TomEE Jakarta project - have we reach the limit?

Thanks everyone. Same feeling here. I think we tried and pushed it as much as we could. What we can do is make sure we fix remaining failures on TCK and support JDK 17 with TomEE. Do a release, branch for maintenance and move master to jakarta. Does it sound like an acceptable plan? -- Jean-Lou

JAXRS TCK Standalone

Hi all, David, it might be more for you lol You spent some significant time on the JAX RS TCK back in May or June. I have managed to clear up most of the issues. The 9 remaining tests failing on JAX RS are for standalone See results https://tck.work/tomee/tests?path=com.sun.ts.tests.jaxrs&build=

Re: JDK 17 - TomEE TCK

I'll dump the information into a specific email thread -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, Oct 5, 2021 at 8:59 AM Zowalla, Richard < richard.zowa...@hs-heilbronn.de> wrote: > No problem. If I can help somehow, let me know :) > > Am Montag, de