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 stay on top of any > CVEs in that release for at least 6 months after 10 goes final so people > have at least a little time to transition +1 By merging both opinions above, the following would be a potential set of steps: - branch 8.0.x - make master 9.0 and rename javax -> jakarta - maintain 8.0 and 9.0 (master) - When 10 is out, keep 10 in master and branch 9.0. - Maintain 8, 9, and master (10) El mar, 5 oct 2021 a las 15:31, David Blevins () escribió: > > On Oct 5, 2021, at 1:59 AM, Thomas Andraschko < > andraschko.tho...@gmail.com> 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 -> 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 > > Agree with making 8 be the branch and 9 be main/master. In terms of how > we handle 9.x, I think we'd want to stay on top of any CVEs in that release > for at least 6 months after 10 goes final so people have at least a little > time to transition over. > > > -David > > > > > > > > Am Di., 5. Okt. 2021 um 10:53 Uhr schrieb Jean-Louis Monteiro < > > jlmonte...@tomitribe.com>: > > > >> 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/jlouismonteiro > >> http://www.tomitribe.com > >> > >> > >> On Tue, Oct 5, 2021 at 10:37 AM Zowalla, Richard < > >> richard.zowa...@hs-heilbronn.de> wrote: > >> > >>> +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 schrieb Jean-Louis Monteiro: > 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-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Tue, Oct 5, 2021 at 7:56 AM David Jencks > > wrote: > > > Maybe even “Our second release _confirmed_…”… > > > > David Jencks > > > >> On Oct 4, 2021, at 12:33 PM, David Blevins < > >> david.blev...@gmail.com> > > wrote: > >>> - Our first release proved releasing both 8 & 9 together can be > > impractical. The TomEE 8 binaries were a dud, only TomEE 9 was > > released. > > There was communication overhead and made for a potentially > > confusing > > release. The TomEE 9 binaries are still very limited. > >>> - Our first release proved releasing both 8 & 9 together can be > > impractical. The TomEE 8 binaries were released, we didn't release > > TomEE > > 9. It's the second time we've done that. We've only managed one > > TomEE 9 > > release in the last 10 months. > >> This was supposed to start "our second > >> release". CopyPasteException :) > >> > >> -David > >> > >>> -- > >>> Richard Zowalla, M.Sc. > >>> Research Associate, PhD Student | Medical Informatics > >>> > >>> Hochschule Heilbronn – University of Applied Sciences > >>> Max-Planck-Str. 39 > >>> D-74081 Heilbronn > >>> phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar) > >>> mail: richard.zowa...@hs-heilbronn.de > >>> web: https://www.mi.hs-heilbronn.de/ > >>> > >> > > -- Atentamente: César Hernández.
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 -> 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 Agree with making 8 be the branch and 9 be main/master. In terms of how we handle 9.x, I think we'd want to stay on top of any CVEs in that release for at least 6 months after 10 goes final so people have at least a little time to transition over. -David > > > Am Di., 5. Okt. 2021 um 10:53 Uhr schrieb Jean-Louis Monteiro < > jlmonte...@tomitribe.com>: > >> 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/jlouismonteiro >> http://www.tomitribe.com >> >> >> On Tue, Oct 5, 2021 at 10:37 AM Zowalla, Richard < >> richard.zowa...@hs-heilbronn.de> wrote: >> >>> +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 schrieb Jean-Louis Monteiro: 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-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, Oct 5, 2021 at 7:56 AM David Jencks wrote: > Maybe even “Our second release _confirmed_…”… > > David Jencks > >> On Oct 4, 2021, at 12:33 PM, David Blevins < >> david.blev...@gmail.com> > wrote: >>> - Our first release proved releasing both 8 & 9 together can be > impractical. The TomEE 8 binaries were a dud, only TomEE 9 was > released. > There was communication overhead and made for a potentially > confusing > release. The TomEE 9 binaries are still very limited. >>> - Our first release proved releasing both 8 & 9 together can be > impractical. The TomEE 8 binaries were released, we didn't release > TomEE > 9. It's the second time we've done that. We've only managed one > TomEE 9 > release in the last 10 months. >> This was supposed to start "our second >> release". CopyPasteException :) >> >> -David >> >>> -- >>> Richard Zowalla, M.Sc. >>> Research Associate, PhD Student | Medical Informatics >>> >>> Hochschule Heilbronn – University of Applied Sciences >>> Max-Planck-Str. 39 >>> D-74081 Heilbronn >>> phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar) >>> mail: richard.zowa...@hs-heilbronn.de >>> web: https://www.mi.hs-heilbronn.de/ >>> >> smime.p7s Description: S/MIME cryptographic signature
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. That’s my 2c. Best Martin — http://twitter.com/mawiesne Am 05.10.2021 um 12:17 schrieb Jean-Louis Monteiro mailto:jlmonte...@tomitribe.com>>: 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...@gmail.com> 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 -> 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 Am Di., 5. Okt. 2021 um 10:53 Uhr schrieb Jean-Louis Monteiro < jlmonte...@tomitribe.com>: 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/jlouismonteiro http://www.tomitribe.com On Tue, Oct 5, 2021 at 10:37 AM Zowalla, Richard < richard.zowa...@hs-heilbronn.de> wrote: +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 schrieb Jean-Louis Monteiro: 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-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, Oct 5, 2021 at 7:56 AM David Jencks < david.a.jen...@gmail.com wrote: Maybe even “Our second release _confirmed_…”… David Jencks On Oct 4, 2021, at 12:33 PM, David Blevins < david.blev...@gmail.com> wrote: - Our first release proved releasing both 8 & 9 together can be impractical. The TomEE 8 binaries were a dud, only TomEE 9 was released. There was communication overhead and made for a potentially confusing release. The TomEE 9 binaries are still very limited. - Our first release proved releasing both 8 & 9 together can be impractical. The TomEE 8 binaries were released, we didn't release TomEE 9. It's the second time we've done that. We've only managed one TomEE 9 release in the last 10 months. This was supposed to start "our second release". CopyPasteException :) -David -- Richard Zowalla, M.Sc. Research Associate, PhD Student | Medical Informatics Hochschule Heilbronn – University of Applied Sciences Max-Planck-Str. 39 D-74081 Heilbronn phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar) mail: richard.zowa...@hs-heilbronn.de web: https://www.mi.hs-heilbronn.de/
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...@gmail.com> 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 -> 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 > > > Am Di., 5. Okt. 2021 um 10:53 Uhr schrieb Jean-Louis Monteiro < > jlmonte...@tomitribe.com>: > > > 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/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Tue, Oct 5, 2021 at 10:37 AM Zowalla, Richard < > > richard.zowa...@hs-heilbronn.de> wrote: > > > > > +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 schrieb Jean-Louis Monteiro: > > > > 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-Louis Monteiro > > > > http://twitter.com/jlouismonteiro > > > > http://www.tomitribe.com > > > > > > > > > > > > On Tue, Oct 5, 2021 at 7:56 AM David Jencks < > david.a.jen...@gmail.com > > > > > > > > > wrote: > > > > > > > > > Maybe even “Our second release _confirmed_…”… > > > > > > > > > > David Jencks > > > > > > > > > > > On Oct 4, 2021, at 12:33 PM, David Blevins < > > > > > > david.blev...@gmail.com> > > > > > wrote: > > > > > > > - Our first release proved releasing both 8 & 9 together can be > > > > > impractical. The TomEE 8 binaries were a dud, only TomEE 9 was > > > > > released. > > > > > There was communication overhead and made for a potentially > > > > > confusing > > > > > release. The TomEE 9 binaries are still very limited. > > > > > > > - Our first release proved releasing both 8 & 9 together can be > > > > > impractical. The TomEE 8 binaries were released, we didn't release > > > > > TomEE > > > > > 9. It's the second time we've done that. We've only managed one > > > > > TomEE 9 > > > > > release in the last 10 months. > > > > > > This was supposed to start "our second > > > > > > release". CopyPasteException :) > > > > > > > > > > > > -David > > > > > > > > > -- > > > Richard Zowalla, M.Sc. > > > Research Associate, PhD Student | Medical Informatics > > > > > > Hochschule Heilbronn – University of Applied Sciences > > > Max-Planck-Str. 39 > > > D-74081 Heilbronn > > > phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar) > > > mail: richard.zowa...@hs-heilbronn.de > > > web: https://www.mi.hs-heilbronn.de/ > > > > > >
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 master - maintain 8.0 and 10.0 and dont maintain the 9.0 branch Am Di., 5. Okt. 2021 um 10:53 Uhr schrieb Jean-Louis Monteiro < jlmonte...@tomitribe.com>: > 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/jlouismonteiro > http://www.tomitribe.com > > > On Tue, Oct 5, 2021 at 10:37 AM Zowalla, Richard < > richard.zowa...@hs-heilbronn.de> wrote: > > > +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 schrieb Jean-Louis Monteiro: > > > 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-Louis Monteiro > > > http://twitter.com/jlouismonteiro > > > http://www.tomitribe.com > > > > > > > > > On Tue, Oct 5, 2021 at 7:56 AM David Jencks > > > > > > wrote: > > > > > > > Maybe even “Our second release _confirmed_…”… > > > > > > > > David Jencks > > > > > > > > > On Oct 4, 2021, at 12:33 PM, David Blevins < > > > > > david.blev...@gmail.com> > > > > wrote: > > > > > > - Our first release proved releasing both 8 & 9 together can be > > > > impractical. The TomEE 8 binaries were a dud, only TomEE 9 was > > > > released. > > > > There was communication overhead and made for a potentially > > > > confusing > > > > release. The TomEE 9 binaries are still very limited. > > > > > > - Our first release proved releasing both 8 & 9 together can be > > > > impractical. The TomEE 8 binaries were released, we didn't release > > > > TomEE > > > > 9. It's the second time we've done that. We've only managed one > > > > TomEE 9 > > > > release in the last 10 months. > > > > > This was supposed to start "our second > > > > > release". CopyPasteException :) > > > > > > > > > > -David > > > > > > > -- > > Richard Zowalla, M.Sc. > > Research Associate, PhD Student | Medical Informatics > > > > Hochschule Heilbronn – University of Applied Sciences > > Max-Planck-Str. 39 > > D-74081 Heilbronn > > phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar) > > mail: richard.zowa...@hs-heilbronn.de > > web: https://www.mi.hs-heilbronn.de/ > > >
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/jlouismonteiro http://www.tomitribe.com On Tue, Oct 5, 2021 at 10:37 AM Zowalla, Richard < richard.zowa...@hs-heilbronn.de> wrote: > +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 schrieb Jean-Louis Monteiro: > > 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-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Tue, Oct 5, 2021 at 7:56 AM David Jencks > > > > wrote: > > > > > Maybe even “Our second release _confirmed_…”… > > > > > > David Jencks > > > > > > > On Oct 4, 2021, at 12:33 PM, David Blevins < > > > > david.blev...@gmail.com> > > > wrote: > > > > > - Our first release proved releasing both 8 & 9 together can be > > > impractical. The TomEE 8 binaries were a dud, only TomEE 9 was > > > released. > > > There was communication overhead and made for a potentially > > > confusing > > > release. The TomEE 9 binaries are still very limited. > > > > > - Our first release proved releasing both 8 & 9 together can be > > > impractical. The TomEE 8 binaries were released, we didn't release > > > TomEE > > > 9. It's the second time we've done that. We've only managed one > > > TomEE 9 > > > release in the last 10 months. > > > > This was supposed to start "our second > > > > release". CopyPasteException :) > > > > > > > > -David > > > > > -- > Richard Zowalla, M.Sc. > Research Associate, PhD Student | Medical Informatics > > Hochschule Heilbronn – University of Applied Sciences > Max-Planck-Str. 39 > D-74081 Heilbronn > phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar) > mail: richard.zowa...@hs-heilbronn.de > web: https://www.mi.hs-heilbronn.de/ >
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 schrieb Jean-Louis Monteiro: > 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-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Tue, Oct 5, 2021 at 7:56 AM David Jencks > > wrote: > > > Maybe even “Our second release _confirmed_…”… > > > > David Jencks > > > > > On Oct 4, 2021, at 12:33 PM, David Blevins < > > > david.blev...@gmail.com> > > wrote: > > > > - Our first release proved releasing both 8 & 9 together can be > > impractical. The TomEE 8 binaries were a dud, only TomEE 9 was > > released. > > There was communication overhead and made for a potentially > > confusing > > release. The TomEE 9 binaries are still very limited. > > > > - Our first release proved releasing both 8 & 9 together can be > > impractical. The TomEE 8 binaries were released, we didn't release > > TomEE > > 9. It's the second time we've done that. We've only managed one > > TomEE 9 > > release in the last 10 months. > > > This was supposed to start "our second > > > release". CopyPasteException :) > > > > > > -David > > > -- Richard Zowalla, M.Sc. Research Associate, PhD Student | Medical Informatics Hochschule Heilbronn – University of Applied Sciences Max-Planck-Str. 39 D-74081 Heilbronn phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar) mail: richard.zowa...@hs-heilbronn.de web: https://www.mi.hs-heilbronn.de/ smime.p7s Description: S/MIME cryptographic signature
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-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, Oct 5, 2021 at 7:56 AM David Jencks wrote: > Maybe even “Our second release _confirmed_…”… > > David Jencks > > > On Oct 4, 2021, at 12:33 PM, David Blevins > wrote: > > > >> - Our first release proved releasing both 8 & 9 together can be > impractical. The TomEE 8 binaries were a dud, only TomEE 9 was released. > There was communication overhead and made for a potentially confusing > release. The TomEE 9 binaries are still very limited. > >> > >> - Our first release proved releasing both 8 & 9 together can be > impractical. The TomEE 8 binaries were released, we didn't release TomEE > 9. It's the second time we've done that. We've only managed one TomEE 9 > release in the last 10 months. > > > > This was supposed to start "our second release". CopyPasteException :) > > > > -David > > > >
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=1633006582993=FAILED >From what I debugged, it looks like a provider issue on the client side. I remember you describe some trickiness around this in our code. If you could have a look or at least provide us with some information, that would be great. I'd like to be 100% compliant on this one and then release TomEE again so we have a JDK 17 compatible binary. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com
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, dem 04.10.2021 um 21:58 +0200 schrieb Jean-Louis Monteiro: > > Yes, I'd like the JAX RS issues to be fixed, because it's a provider > > ordering or discovery issue on the client side. > > It's taking a bit of time, I'm sorry > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Mon, Oct 4, 2021 at 11:38 AM Zowalla, Richard < > > richard.zowa...@hs-heilbronn.de> wrote: > > > > > Hi, > > > > > > thanks for the J17 work - the TCK looks indeed very promising & > > > good. > > > > > > I am wondering, if we should have a (fast) 8.0.9 to support JDK-17 > > > for > > > end-users? > > > > > > Gruss > > > Richard > > > > > > Am Donnerstag, dem 30.09.2021 um 10:43 +0200 schrieb Jean-Louis > > > Monteiro: > > > > Hi all, > > > > > > > > Been trying to look at our support for JDK 17. > > > > Jon and I worked on some fixes on TomEE and the TCK side to > > > > support > > > > JDK 17. > > > > > > > > We aren't looking bad at all. The TCK runs with TomEE 8 and EE 8 > > > > looks good > > > > and at the same level as with JDK 8 and JDK 11. > > > > > > > > Results available here https://tck.work/tomee/project?id=8 > > > > > > > > For TomEE 9 and EE 9, the build just started > > > > > > > > Results will be available here > > > > https://tck.work/tomee/project?id=17189 > > > > > > > > -- > > > > Jean-Louis Monteiro > > > > http://twitter.com/jlouismonteiro > > > > http://www.tomitribe.com > -- > Richard Zowalla, M.Sc. > Research Associate, PhD Student | Medical Informatics > > Hochschule Heilbronn – University of Applied Sciences > Max-Planck-Str. 39 > D-74081 Heilbronn > phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar) > mail: richard.zowa...@hs-heilbronn.de > web: https://www.mi.hs-heilbronn.de/ >
Re: JDK 17 - TomEE TCK
No problem. If I can help somehow, let me know :) Am Montag, dem 04.10.2021 um 21:58 +0200 schrieb Jean-Louis Monteiro: > Yes, I'd like the JAX RS issues to be fixed, because it's a provider > ordering or discovery issue on the client side. > It's taking a bit of time, I'm sorry > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Mon, Oct 4, 2021 at 11:38 AM Zowalla, Richard < > richard.zowa...@hs-heilbronn.de> wrote: > > > Hi, > > > > thanks for the J17 work - the TCK looks indeed very promising & > > good. > > > > I am wondering, if we should have a (fast) 8.0.9 to support JDK-17 > > for > > end-users? > > > > Gruss > > Richard > > > > Am Donnerstag, dem 30.09.2021 um 10:43 +0200 schrieb Jean-Louis > > Monteiro: > > > Hi all, > > > > > > Been trying to look at our support for JDK 17. > > > Jon and I worked on some fixes on TomEE and the TCK side to > > > support > > > JDK 17. > > > > > > We aren't looking bad at all. The TCK runs with TomEE 8 and EE 8 > > > looks good > > > and at the same level as with JDK 8 and JDK 11. > > > > > > Results available here https://tck.work/tomee/project?id=8 > > > > > > For TomEE 9 and EE 9, the build just started > > > > > > Results will be available here > > > https://tck.work/tomee/project?id=17189 > > > > > > -- > > > Jean-Louis Monteiro > > > http://twitter.com/jlouismonteiro > > > http://www.tomitribe.com -- Richard Zowalla, M.Sc. Research Associate, PhD Student | Medical Informatics Hochschule Heilbronn – University of Applied Sciences Max-Planck-Str. 39 D-74081 Heilbronn phone: +49 7131 504 6791 (zur Zeit nicht via Telefon erreichbar) mail: richard.zowa...@hs-heilbronn.de web: https://www.mi.hs-heilbronn.de/ smime.p7s Description: S/MIME cryptographic signature
