Re: TomEE 9.x - from javax to jakarta namespace
Hi, thanks Jean-Louis, I've tried replacing "geronimo specs" dependencies with "jakartaee apis" dependencies, while this does allow to easily exclude implementations jars, it could also have an impact on the OSGI system used by TomEE to locate services. (it seems its only used to locate the EJB container, am i right ?) i would like to be able to replace the geronimo osgi locator by a custom one for TomEE, but i currently can't on my own. though, i could provide a gist file for the POM dependencies changes (possibly no geronimo deps in the end). if someone else is willing to jump on this adventure with me they're welcome. --- Swell. side note, i cant build the "tomee-jakarta" project i'm working on my windows, so i'll try on a mac later. cant submit a PR atm but still trying things. On Mon, 11 Jul 2022 at 11:50, Jean-Louis Monteiro wrote: > Hi Swell; > > You answer and thoughts are more than welcome. > > For the moment we use the same approach, exclude APIs where the IMPL is > packaged in (Mail and Faces at least). > Yes Jakarta also provides an Uber jar, and regardless of the fact it is > outdated or not, it has the same issue. Using the Uber jar automatically > brings use Sun Mail implementation and Faces Mojorra implementation. > > i believe there could be : > > > >- one up to date bom for all api only. > > > Does not seem to solve the issue as the dependency for the API would also > bring the implementation because it's one jar only and one dependency only. > > > >- one uber apis jar per TomEE flavor. > > > Yes I was thinking about this one as well. > > > >- separated original implementation jars from providers. > > > We would need to dig into the specifics to see if that is possible and how. > > > Yes feel free to submit a PR and ping us on the mailing list to get > feedback and reviews. > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Wed, Jul 6, 2022 at 11:27 AM Swell wrote: > > > Hi, regarding the APIs > > > > i hope that my answer is not off-topic, what I believe is someone using > our > > uber api jar would want the apis without impl, even for mail and faces. > > if i were to use it i would want implementations separated on their own > > official jar, but not fused together. > > > > as a note there exist a bom for jakarta ee but its outdated > > > > > https://mvnrepository.com/artifact/jakarta.platform/jakarta.jakartaee-bom/9.1.0 > > the official one provided lacks the minor fixes (e.g points to EJB 4.0.0 > > instead of 4.0.1, to cite only one of the problems) > > > > i believe there could be : > > > >- one up to date bom for all api only. > >- one uber apis jar per TomEE flavor. > >- separated original implementation jars from providers. > > > > we provide an up-to-date jakarta ee javadoc to cover the lack (which i > > updated the api versions), in the same idea > > would it be ok for TomEE project to provide both such a BOM and uber apis > > jar ? (which i could update side by side with javadoc) > > > > -- > > Swell > > > > On Mon, 4 Jul 2022 at 10:50, Jean-Louis Monteiro < > jlmonte...@tomitribe.com > > > > > wrote: > > > > > Hi, > > > > > > Bumping this thread up > > > Not yet at the point where I'm clear on what path to use regarding the > > API, > > > but it's been a while so I wanted to provide some status. > > > > > > You may have noticed the VOTE thread going on regarding TomEE 9.0.0-M2. > > > This is the first real milestone for TomEE with the actual source code > > > migrated to jakarta. It means that full packaged distributions > > (WebProfile, > > > MicroProfile, Plume and Plus ZIP/TAR.GZ) should be mostly working. But > > the > > > application composer, the JUnit support, even Arquillian are now > fullyHi, > > > migrated. We had to do a lot of shading/relocation of certain libraries > > on > > > our side because libraries were not yet ready. > > > > > > We've worked very hard but we are finally looking good. We still have a > > few > > > failures on our build to solve, but the platform TCK + CDI + BVal are > > > looking good with less than 50 failures of 35K tests. > > > > > > Please remember this is a milestone and we are all still working on it. > > Any > > > feedback is appreciated and will help. > > > > > > We started also upgrading our MicroProfile support to the latest one. > So > > > far Config, Health and Metrics are fully migrated and passing the TCK. > We > > > are actively working on MicroProfile JWT. And we'll be proceeding with > > the > > > others when possible. > > > > > > If you haven't done it yet, please try it and feel free to vote. > > > > > > -- > > > Jean-Louis Monteiro > > > http://twitter.com/jlouismonteiro > > > http://www.tomitribe.com > > > > > > > > > On Thu, May 26, 2022 at 1:28 PM Jean-Louis Monteiro < > > > jlmonte...@tomitribe.com> wrote: > > > > > > > Hi, > > > > > > > > quick feedback before getting into more details > > > > > > > > A/ or this alternative > > > >
Re: TomEE 9.x - from javax to jakarta namespace
Hi Swell; You answer and thoughts are more than welcome. For the moment we use the same approach, exclude APIs where the IMPL is packaged in (Mail and Faces at least). Yes Jakarta also provides an Uber jar, and regardless of the fact it is outdated or not, it has the same issue. Using the Uber jar automatically brings use Sun Mail implementation and Faces Mojorra implementation. i believe there could be : > >- one up to date bom for all api only. > Does not seem to solve the issue as the dependency for the API would also bring the implementation because it's one jar only and one dependency only. >- one uber apis jar per TomEE flavor. > Yes I was thinking about this one as well. >- separated original implementation jars from providers. > We would need to dig into the specifics to see if that is possible and how. Yes feel free to submit a PR and ping us on the mailing list to get feedback and reviews. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Wed, Jul 6, 2022 at 11:27 AM Swell wrote: > Hi, regarding the APIs > > i hope that my answer is not off-topic, what I believe is someone using our > uber api jar would want the apis without impl, even for mail and faces. > if i were to use it i would want implementations separated on their own > official jar, but not fused together. > > as a note there exist a bom for jakarta ee but its outdated > > https://mvnrepository.com/artifact/jakarta.platform/jakarta.jakartaee-bom/9.1.0 > the official one provided lacks the minor fixes (e.g points to EJB 4.0.0 > instead of 4.0.1, to cite only one of the problems) > > i believe there could be : > >- one up to date bom for all api only. >- one uber apis jar per TomEE flavor. >- separated original implementation jars from providers. > > we provide an up-to-date jakarta ee javadoc to cover the lack (which i > updated the api versions), in the same idea > would it be ok for TomEE project to provide both such a BOM and uber apis > jar ? (which i could update side by side with javadoc) > > -- > Swell > > On Mon, 4 Jul 2022 at 10:50, Jean-Louis Monteiro > > wrote: > > > Hi, > > > > Bumping this thread up > > Not yet at the point where I'm clear on what path to use regarding the > API, > > but it's been a while so I wanted to provide some status. > > > > You may have noticed the VOTE thread going on regarding TomEE 9.0.0-M2. > > This is the first real milestone for TomEE with the actual source code > > migrated to jakarta. It means that full packaged distributions > (WebProfile, > > MicroProfile, Plume and Plus ZIP/TAR.GZ) should be mostly working. But > the > > application composer, the JUnit support, even Arquillian are now fullyHi, > > migrated. We had to do a lot of shading/relocation of certain libraries > on > > our side because libraries were not yet ready. > > > > We've worked very hard but we are finally looking good. We still have a > few > > failures on our build to solve, but the platform TCK + CDI + BVal are > > looking good with less than 50 failures of 35K tests. > > > > Please remember this is a milestone and we are all still working on it. > Any > > feedback is appreciated and will help. > > > > We started also upgrading our MicroProfile support to the latest one. So > > far Config, Health and Metrics are fully migrated and passing the TCK. We > > are actively working on MicroProfile JWT. And we'll be proceeding with > the > > others when possible. > > > > If you haven't done it yet, please try it and feel free to vote. > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Thu, May 26, 2022 at 1:28 PM Jean-Louis Monteiro < > > jlmonte...@tomitribe.com> wrote: > > > > > Hi, > > > > > > quick feedback before getting into more details > > > > > > A/ or this alternative > > > Geronimo Specs were not available in the Jakarta namespace. We are > > > starting to move some of them like Activation and Mail. Other than > that, > > we > > > mainly have Eclipse produced APIs for Jakarta. > > > I'm not sure if we want to migrate our Geronimo Specs jars or use the > > > stock Jakarta APIs. Important note, if we do, we may not need the > > > jakartaee-api because there is already a Uber jar for Jakarta within > the > > > different profiles. Should we get our user to use it as provided. And > on > > > our side, should we create just a bom in our project and get the job > > done? > > > > > > Some APIs are also more or less implementations and vice versa. This is > > > the case for mail, faces, and some more as you mentioned. I'm fine > > > including Mail provider + Geronimo Mail spec in the jakartaee-api jar > but > > > mind that in the past some users wanted to use Sun implementation and > it > > > will be harder > > > > > > D/ what about inconsistencies like ... > > > Some implementations can be switched, for example Faces. Which is also > a > > > mess because API and IMPL are linked together.
Re: TomEE 9.x - from javax to jakarta namespace
Hi, regarding the APIs i hope that my answer is not off-topic, what I believe is someone using our uber api jar would want the apis without impl, even for mail and faces. if i were to use it i would want implementations separated on their own official jar, but not fused together. as a note there exist a bom for jakarta ee but its outdated https://mvnrepository.com/artifact/jakarta.platform/jakarta.jakartaee-bom/9.1.0 the official one provided lacks the minor fixes (e.g points to EJB 4.0.0 instead of 4.0.1, to cite only one of the problems) i believe there could be : - one up to date bom for all api only. - one uber apis jar per TomEE flavor. - separated original implementation jars from providers. we provide an up-to-date jakarta ee javadoc to cover the lack (which i updated the api versions), in the same idea would it be ok for TomEE project to provide both such a BOM and uber apis jar ? (which i could update side by side with javadoc) -- Swell On Mon, 4 Jul 2022 at 10:50, Jean-Louis Monteiro wrote: > Hi, > > Bumping this thread up > Not yet at the point where I'm clear on what path to use regarding the API, > but it's been a while so I wanted to provide some status. > > You may have noticed the VOTE thread going on regarding TomEE 9.0.0-M2. > This is the first real milestone for TomEE with the actual source code > migrated to jakarta. It means that full packaged distributions (WebProfile, > MicroProfile, Plume and Plus ZIP/TAR.GZ) should be mostly working. But the > application composer, the JUnit support, even Arquillian are now fullyHi, > migrated. We had to do a lot of shading/relocation of certain libraries on > our side because libraries were not yet ready. > > We've worked very hard but we are finally looking good. We still have a few > failures on our build to solve, but the platform TCK + CDI + BVal are > looking good with less than 50 failures of 35K tests. > > Please remember this is a milestone and we are all still working on it. Any > feedback is appreciated and will help. > > We started also upgrading our MicroProfile support to the latest one. So > far Config, Health and Metrics are fully migrated and passing the TCK. We > are actively working on MicroProfile JWT. And we'll be proceeding with the > others when possible. > > If you haven't done it yet, please try it and feel free to vote. > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Thu, May 26, 2022 at 1:28 PM Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > > > Hi, > > > > quick feedback before getting into more details > > > > A/ or this alternative > > Geronimo Specs were not available in the Jakarta namespace. We are > > starting to move some of them like Activation and Mail. Other than that, > we > > mainly have Eclipse produced APIs for Jakarta. > > I'm not sure if we want to migrate our Geronimo Specs jars or use the > > stock Jakarta APIs. Important note, if we do, we may not need the > > jakartaee-api because there is already a Uber jar for Jakarta within the > > different profiles. Should we get our user to use it as provided. And on > > our side, should we create just a bom in our project and get the job > done? > > > > Some APIs are also more or less implementations and vice versa. This is > > the case for mail, faces, and some more as you mentioned. I'm fine > > including Mail provider + Geronimo Mail spec in the jakartaee-api jar but > > mind that in the past some users wanted to use Sun implementation and it > > will be harder > > > > D/ what about inconsistencies like ... > > Some implementations can be switched, for example Faces. Which is also a > > mess because API and IMPL are linked together. I had previously the Faces > > API but of course you need the implementation as well, same as for mail. > > But Plume uses Mojorra. So we are in the situation where we need to pick > > one or the other. > > > > B/ or this alternative ... > > Tomcat classifier because we don't want to cheap with APIs already > > provided in Tomcat with the risk of not being fully aligned. So we use > > Tomcat APIs. Should we go the way around and remove Tomcat APIs from the > > final distribution and get rid of the Tomcat classifier? > > > > Note sure if my reply is clear, hopefully it helps. > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Thu, May 26, 2022 at 3:23 AM David Blevins > > wrote: > > > >> Thanks so much for this. I even started creating one myself early this > >> morning, ... then the rest of the day happened LOL > >> > >> > On May 25, 2022, at 1:56 PM, Jean-Louis Monteiro < > >> jlmonte...@tomitribe.com> wrote: > >> > > >> > Here it is > >> > > >> > https://gist.github.com/jeanouii/9bb6c14bdde227e2fed83fd73db3a646/revisions > >> > >> Looks like we've yanked out Faces, JSTL, Mail, etc. I suspect we're > >> trying to hit the line of not including APIs that are implementations. > The
Re: TomEE 9.x - from javax to jakarta namespace
Forgot the big thank you to everyone and special kudos to Richard. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Mon, Jul 4, 2022 at 10:49 AM Jean-Louis Monteiro < jlmonte...@tomitribe.com> wrote: > Hi, > > Bumping this thread up > Not yet at the point where I'm clear on what path to use regarding the > API, but it's been a while so I wanted to provide some status. > > You may have noticed the VOTE thread going on regarding TomEE 9.0.0-M2. > This is the first real milestone for TomEE with the actual source code > migrated to jakarta. It means that full packaged distributions (WebProfile, > MicroProfile, Plume and Plus ZIP/TAR.GZ) should be mostly working. But the > application composer, the JUnit support, even Arquillian are now fully > migrated. We had to do a lot of shading/relocation of certain libraries on > our side because libraries were not yet ready. > > We've worked very hard but we are finally looking good. We still have a > few failures on our build to solve, but the platform TCK + CDI + BVal are > looking good with less than 50 failures of 35K tests. > > Please remember this is a milestone and we are all still working on it. > Any feedback is appreciated and will help. > > We started also upgrading our MicroProfile support to the latest one. So > far Config, Health and Metrics are fully migrated and passing the TCK. We > are actively working on MicroProfile JWT. And we'll be proceeding with the > others when possible. > > If you haven't done it yet, please try it and feel free to vote. > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Thu, May 26, 2022 at 1:28 PM Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > >> Hi, >> >> quick feedback before getting into more details >> >> A/ or this alternative >> Geronimo Specs were not available in the Jakarta namespace. We are >> starting to move some of them like Activation and Mail. Other than that, we >> mainly have Eclipse produced APIs for Jakarta. >> I'm not sure if we want to migrate our Geronimo Specs jars or use the >> stock Jakarta APIs. Important note, if we do, we may not need the >> jakartaee-api because there is already a Uber jar for Jakarta within the >> different profiles. Should we get our user to use it as provided. And on >> our side, should we create just a bom in our project and get the job done? >> >> Some APIs are also more or less implementations and vice versa. This is >> the case for mail, faces, and some more as you mentioned. I'm fine >> including Mail provider + Geronimo Mail spec in the jakartaee-api jar but >> mind that in the past some users wanted to use Sun implementation and it >> will be harder >> >> D/ what about inconsistencies like ... >> Some implementations can be switched, for example Faces. Which is also a >> mess because API and IMPL are linked together. I had previously the Faces >> API but of course you need the implementation as well, same as for mail. >> But Plume uses Mojorra. So we are in the situation where we need to pick >> one or the other. >> >> B/ or this alternative ... >> Tomcat classifier because we don't want to cheap with APIs already >> provided in Tomcat with the risk of not being fully aligned. So we use >> Tomcat APIs. Should we go the way around and remove Tomcat APIs from the >> final distribution and get rid of the Tomcat classifier? >> >> Note sure if my reply is clear, hopefully it helps. >> >> -- >> Jean-Louis Monteiro >> http://twitter.com/jlouismonteiro >> http://www.tomitribe.com >> >> >> On Thu, May 26, 2022 at 3:23 AM David Blevins >> wrote: >> >>> Thanks so much for this. I even started creating one myself early this >>> morning, ... then the rest of the day happened LOL >>> >>> > On May 25, 2022, at 1:56 PM, Jean-Louis Monteiro < >>> jlmonte...@tomitribe.com> wrote: >>> > >>> > Here it is >>> > >>> https://gist.github.com/jeanouii/9bb6c14bdde227e2fed83fd73db3a646/revisions >>> >>> Looks like we've yanked out Faces, JSTL, Mail, etc. I suspect we're >>> trying to hit the line of not including APIs that are implementations. The >>> real trick is even HttpServlet is completely dependent on the servlet >>> container in the same way Faces, Mail, JSTL, etc are dependent on their >>> implementations. I'm not too sure if Activation is also considered an >>> implementation as well -- I'm not sure off-hand if there is a separate >>> implementation jar. >>> >>> I know we didn't include mail in our javaee-api jar, so excluding is >>> following that logic. I also know we have the >>> jakartaee-api-9.1-M2-SNAPSHOT-tomcat.jar, which cuts out everything very >>> close to the way we've now done it in jakartaee-api-9.1-M2-SNAPSHOT.jar >>> >>> How do we want to handle this? >>> >>> Seems our options are: >>> >>> A. Leave jakartaee-api-X.jar and jakartaee-api-X-tomcat.jar nearly >>> identical in missing many specs. There is no uber jar people can compile >>> against that has most
Re: TomEE 9.x - from javax to jakarta namespace
Hi, Bumping this thread up Not yet at the point where I'm clear on what path to use regarding the API, but it's been a while so I wanted to provide some status. You may have noticed the VOTE thread going on regarding TomEE 9.0.0-M2. This is the first real milestone for TomEE with the actual source code migrated to jakarta. It means that full packaged distributions (WebProfile, MicroProfile, Plume and Plus ZIP/TAR.GZ) should be mostly working. But the application composer, the JUnit support, even Arquillian are now fully migrated. We had to do a lot of shading/relocation of certain libraries on our side because libraries were not yet ready. We've worked very hard but we are finally looking good. We still have a few failures on our build to solve, but the platform TCK + CDI + BVal are looking good with less than 50 failures of 35K tests. Please remember this is a milestone and we are all still working on it. Any feedback is appreciated and will help. We started also upgrading our MicroProfile support to the latest one. So far Config, Health and Metrics are fully migrated and passing the TCK. We are actively working on MicroProfile JWT. And we'll be proceeding with the others when possible. If you haven't done it yet, please try it and feel free to vote. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Thu, May 26, 2022 at 1:28 PM Jean-Louis Monteiro < jlmonte...@tomitribe.com> wrote: > Hi, > > quick feedback before getting into more details > > A/ or this alternative > Geronimo Specs were not available in the Jakarta namespace. We are > starting to move some of them like Activation and Mail. Other than that, we > mainly have Eclipse produced APIs for Jakarta. > I'm not sure if we want to migrate our Geronimo Specs jars or use the > stock Jakarta APIs. Important note, if we do, we may not need the > jakartaee-api because there is already a Uber jar for Jakarta within the > different profiles. Should we get our user to use it as provided. And on > our side, should we create just a bom in our project and get the job done? > > Some APIs are also more or less implementations and vice versa. This is > the case for mail, faces, and some more as you mentioned. I'm fine > including Mail provider + Geronimo Mail spec in the jakartaee-api jar but > mind that in the past some users wanted to use Sun implementation and it > will be harder > > D/ what about inconsistencies like ... > Some implementations can be switched, for example Faces. Which is also a > mess because API and IMPL are linked together. I had previously the Faces > API but of course you need the implementation as well, same as for mail. > But Plume uses Mojorra. So we are in the situation where we need to pick > one or the other. > > B/ or this alternative ... > Tomcat classifier because we don't want to cheap with APIs already > provided in Tomcat with the risk of not being fully aligned. So we use > Tomcat APIs. Should we go the way around and remove Tomcat APIs from the > final distribution and get rid of the Tomcat classifier? > > Note sure if my reply is clear, hopefully it helps. > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Thu, May 26, 2022 at 3:23 AM David Blevins > wrote: > >> Thanks so much for this. I even started creating one myself early this >> morning, ... then the rest of the day happened LOL >> >> > On May 25, 2022, at 1:56 PM, Jean-Louis Monteiro < >> jlmonte...@tomitribe.com> wrote: >> > >> > Here it is >> > >> https://gist.github.com/jeanouii/9bb6c14bdde227e2fed83fd73db3a646/revisions >> >> Looks like we've yanked out Faces, JSTL, Mail, etc. I suspect we're >> trying to hit the line of not including APIs that are implementations. The >> real trick is even HttpServlet is completely dependent on the servlet >> container in the same way Faces, Mail, JSTL, etc are dependent on their >> implementations. I'm not too sure if Activation is also considered an >> implementation as well -- I'm not sure off-hand if there is a separate >> implementation jar. >> >> I know we didn't include mail in our javaee-api jar, so excluding is >> following that logic. I also know we have the >> jakartaee-api-9.1-M2-SNAPSHOT-tomcat.jar, which cuts out everything very >> close to the way we've now done it in jakartaee-api-9.1-M2-SNAPSHOT.jar >> >> How do we want to handle this? >> >> Seems our options are: >> >> A. Leave jakartaee-api-X.jar and jakartaee-api-X-tomcat.jar nearly >> identical in missing many specs. There is no uber jar people can compile >> against that has most everything. People would need to discover which >> specs are missing and pull them in individually. >> >> B. Eliminate having two jars, there is now just >> jakartaee-api-X-tomcat.jar (which we call jakartaee-api-X.jar). There is >> no uber jar people can compile against that has most everything. People >> would need to discover which specs are missing and pull them in >>
Re: Jakarta Mail TCK - Additional Thoughts? (was: TomEE 9.x - from javax to jakarta namespace)
hrieb Zowalla, > > > Richard: > > > > To give a more detailed view / update from the spec tck party > > > > regarding > > > > activation and mail: > > > > > > > > (A) Geronimo Activation 2.0 > > > > > > > > After a first milestone (M1) and some additional fixes after > > > > running > > > > the activation TCK [1] and related signatures tests, we are now > > > > passing > > > > them. > > > > > > > > JL prepared a release artifact (1.0.0), which is currently > > > > under > > > > vote. > > > > > > > > During the tck work, we found some inconsistency / unspecified > > > > behaviour of "normalizeMimeTypeParameter" of > > > > ActivationDataFlavor. > > > > While this method is tested in the TCK on the basis of the > > > > reference > > > > implementation neither the spec itself nor the javadoc are > > > > really > > > > clear > > > > about the "right" return value. At the moment, we adjusted it > > > > to > > > > pass > > > > the TCK test in question. > > > > > > > > There is an ongoing discussion at dev@geronimo if this is a > > > > desired > > > > behaviour or if a system property should be introduced in order > > > > to > > > > reduce the possibility of breaking some users. > > > > > > > > (B) Geronimo Mail 2.0 / 2.1 > > > > > > > > The current mail impl has some TCK failures. It seems, that we > > > > need > > > > to > > > > do some additional work to get it compliant with the standalone > > > > mail > > > > tck [3]. > > > > > > > > The signature tests are failing for Java 11 but are fine with > > > > Java > > > > 8 > > > > [4] due to some usage of Object#finalize() and missing > > > > annotations > > > > (only available in Java 9+) in the Geronimo implementation. > > > > While > > > > it > > > > is > > > > not that important for EE9, we need to keep it in mind for > > > > EE10. > > > > > > > > We currently pass 166 out of 321 mail tck tests [5]. I guess, > > > > we > > > > need > > > > to give it some more love to get the numbers up and finally get > > > > it > > > > to > > > > pass the mail tck. The good thing is, that we already pass the > > > > javamail > > > > tests for TomEE [6]. > > > > > > > > Gruß > > > > Richard > > > > > > > > > > > > > > > > [1] https://jakarta.ee/specifications/activation/2.0/ > > > > [2] > > > > https://lists.apache.org/thread/h8twm4rmdxt67fx227nyywjp96b6cky1 > > > > [3] https://jakarta.ee/specifications/mail/2.0/ > > > > [4] https://issues.apache.org/jira/browse/GERONIMO-6834 > > > > [5] https://issues.apache.org/jira/browse/GERONIMO-6835 > > > > [6] > > > > > > https://tck.work/tomee/tests?build=1651841331620=com.sun.ts.tests.javamail > > > > Am Dienstag, dem 24.05.2022 um 15:44 +0200 schrieb Jean-Louis > > > > Monteiro: > > > > > Alright, time for a new update. > > > > > > > > > > TomEE 8.x with JDK8 and EE8 is equivalent to TomEE 9.x with > > > > > JDK11/JDK17 and > > > > > EE9. > > > > > The build is still not full green, but it's time to start > > > > > grabbing > > > > > user > > > > > feedback as we discussed. > > > > > > > > > > So the work started to take every single piece we fixed or > > > > > patched > > > > > to > > > > > start > > > > > doing releases and if possible run TCK + signature Tests. > > > > > > > > > > David did activation and mail milestones. Richard used the > > > > > milestone > > > > > to fix > > > > > and we are now under vote for activation 2.0 final and > > > > > Richard is > > > > > making > > > > > some awesomeness on the mail spec and impl. We should be able > > > > > to > > > > > get > > > > > final > > > > > versions soon. > > > > &g
Re: Jakarta Mail TCK - Additional Thoughts? (was: TomEE 9.x - from javax to jakarta namespace)
; > about the "right" return value. At the moment, we adjusted it to > > > pass > > > the TCK test in question. > > > > > > There is an ongoing discussion at dev@geronimo if this is a desired > > > behaviour or if a system property should be introduced in order to > > > reduce the possibility of breaking some users. > > > > > > (B) Geronimo Mail 2.0 / 2.1 > > > > > > The current mail impl has some TCK failures. It seems, that we need > > > to > > > do some additional work to get it compliant with the standalone > > > mail > > > tck [3]. > > > > > > The signature tests are failing for Java 11 but are fine with Java > > > 8 > > > [4] due to some usage of Object#finalize() and missing annotations > > > (only available in Java 9+) in the Geronimo implementation. While > > > it > > > is > > > not that important for EE9, we need to keep it in mind for EE10. > > > > > > We currently pass 166 out of 321 mail tck tests [5]. I guess, we > > > need > > > to give it some more love to get the numbers up and finally get it > > > to > > > pass the mail tck. The good thing is, that we already pass the > > > javamail > > > tests for TomEE [6]. > > > > > > Gruß > > > Richard > > > > > > > > > > > > [1] https://jakarta.ee/specifications/activation/2.0/ > > > [2] > > > https://lists.apache.org/thread/h8twm4rmdxt67fx227nyywjp96b6cky1 > > > [3] https://jakarta.ee/specifications/mail/2.0/ > > > [4] https://issues.apache.org/jira/browse/GERONIMO-6834 > > > [5] https://issues.apache.org/jira/browse/GERONIMO-6835 > > > [6] > > > > https://tck.work/tomee/tests?build=1651841331620=com.sun.ts.tests.javamail > > > > > > Am Dienstag, dem 24.05.2022 um 15:44 +0200 schrieb Jean-Louis > > > Monteiro: > > > > Alright, time for a new update. > > > > > > > > TomEE 8.x with JDK8 and EE8 is equivalent to TomEE 9.x with > > > > JDK11/JDK17 and > > > > EE9. > > > > The build is still not full green, but it's time to start > > > > grabbing > > > > user > > > > feedback as we discussed. > > > > > > > > So the work started to take every single piece we fixed or > > > > patched > > > > to > > > > start > > > > doing releases and if possible run TCK + signature Tests. > > > > > > > > David did activation and mail milestones. Richard used the > > > > milestone > > > > to fix > > > > and we are now under vote for activation 2.0 final and Richard is > > > > making > > > > some awesomeness on the mail spec and impl. We should be able to > > > > get > > > > final > > > > versions soon. > > > > > > > > We also have an OWB vote starting today for a jakarta compatible > > > > version > > > > (including TCK). > > > > Next step is to release a milestone for jakartaee-api 9.1-M2 and > > > > move > > > > on. > > > > > > > > > > > > > > > > -- > > > > Jean-Louis Monteiro > > > > http://twitter.com/jlouismonteiro > > > > http://www.tomitribe.com > > > > > > > > > > > > On Thu, May 12, 2022 at 9:29 AM Wiesner, Martin < > > > > martin.wies...@hs-heilbronn.de> wrote: > > > > > > > > > +1 > > > > > > > > > > Best > > > > > Martin > > > > > — > > > > > https://twitter.com/mawiesne > > > > > > > > > > > > > > > Am 11.05.2022 um 19:00 schrieb Cesar Hernandez < > > > > > cesargu...@gmail.com > > > > > <mailto:cesargu...@gmail.com>>: > > > > > > > > > > +1, Thank you! > > > > > > > > > > > > > > > El mié, 11 may 2022 a las 9:06, Daniel Dias Dos Santos (< > > > > > daniel.dias.analist...@gmail.com > > > > daniel.dias.analist...@gmail.com>>) > > > > > escribió: > > > > > > > > > > +1 > > > > > > > > > > On Wed, May 11, 2022, 12:00 Zowalla, Richard < > > > > > richard.zowa...@hs-heilbronn.de > > > > richard.zowa...@hs-heilbronn.de>&
Re: Jakarta Mail TCK - Additional Thoughts? (was: TomEE 9.x - from javax to jakarta namespace)
javamail > > tests for TomEE [6]. > > > > Gruß > > Richard > > > > > > > > [1] https://jakarta.ee/specifications/activation/2.0/ > > [2] > > https://lists.apache.org/thread/h8twm4rmdxt67fx227nyywjp96b6cky1 > > [3] https://jakarta.ee/specifications/mail/2.0/ > > [4] https://issues.apache.org/jira/browse/GERONIMO-6834 > > [5] https://issues.apache.org/jira/browse/GERONIMO-6835 > > [6] > > https://tck.work/tomee/tests?build=1651841331620=com.sun.ts.tests.javamail > > > > Am Dienstag, dem 24.05.2022 um 15:44 +0200 schrieb Jean-Louis > > Monteiro: > > > Alright, time for a new update. > > > > > > TomEE 8.x with JDK8 and EE8 is equivalent to TomEE 9.x with > > > JDK11/JDK17 and > > > EE9. > > > The build is still not full green, but it's time to start > > > grabbing > > > user > > > feedback as we discussed. > > > > > > So the work started to take every single piece we fixed or > > > patched > > > to > > > start > > > doing releases and if possible run TCK + signature Tests. > > > > > > David did activation and mail milestones. Richard used the > > > milestone > > > to fix > > > and we are now under vote for activation 2.0 final and Richard is > > > making > > > some awesomeness on the mail spec and impl. We should be able to > > > get > > > final > > > versions soon. > > > > > > We also have an OWB vote starting today for a jakarta compatible > > > version > > > (including TCK). > > > Next step is to release a milestone for jakartaee-api 9.1-M2 and > > > move > > > on. > > > > > > > > > > > > -- > > > Jean-Louis Monteiro > > > http://twitter.com/jlouismonteiro > > > http://www.tomitribe.com > > > > > > > > > On Thu, May 12, 2022 at 9:29 AM Wiesner, Martin < > > > martin.wies...@hs-heilbronn.de> wrote: > > > > > > > +1 > > > > > > > > Best > > > > Martin > > > > — > > > > https://twitter.com/mawiesne > > > > > > > > > > > > Am 11.05.2022 um 19:00 schrieb Cesar Hernandez < > > > > cesargu...@gmail.com > > > > <mailto:cesargu...@gmail.com>>: > > > > > > > > +1, Thank you! > > > > > > > > > > > > El mié, 11 may 2022 a las 9:06, Daniel Dias Dos Santos (< > > > > daniel.dias.analist...@gmail.com > > > daniel.dias.analist...@gmail.com>>) > > > > escribió: > > > > > > > > +1 > > > > > > > > On Wed, May 11, 2022, 12:00 Zowalla, Richard < > > > > richard.zowa...@hs-heilbronn.de > > > richard.zowa...@hs-heilbronn.de>> > > > > wrote: > > > > > > > > I am fine with it: +1 > > > > > > > > Von: Jean-Louis Monteiro > > > jlmonte...@tomitribe.com>> > > > > Gesendet: Mittwoch, 11. Mai 2022 15:57:54 > > > > An: dev@tomee.apache.org<mailto:dev@tomee.apache.org> > > > > Betreff: Re: TomEE 9.x - from javax to jakarta namespace > > > > > > > > Alright, with the latest changes pushed yesterday and today, we > > > > are > > > > now > > > > at > > > > the exact same numbers for TomEE 8.x / Jakarta EE 8 under JDK8 > > > > and > > > > TomEE > > > > 9.x / Jakarta 9.1 under JDK17. > > > > > > > > If everyone is ok with it, we can create a new milestone and > > > > give > > > > users > > > > the > > > > opportunity to provide us with some feedback and to report > > > > bugs. > > > > > > > > -- > > > > Jean-Louis Monteiro > > > > http://twitter.com/jlouismonteiro > > > > http://www.tomitribe.com > > > > > > > > > > > > On Tue, May 10, 2022 at 7:06 PM David Blevins < > > > > david.blev...@gmail.com> > > > > wrote: > > > > > > > > Was checking out the TCK numbers this morning can make to > > > > suggest > > > > a > > > > 9.0.0-M8 while things look good and found this amazing email. > > > > > > > > The 9.0.x branch is looking absolutely amazing!!!
Re: TomEE 9.x - from javax to jakarta namespace
Hi, quick feedback before getting into more details A/ or this alternative Geronimo Specs were not available in the Jakarta namespace. We are starting to move some of them like Activation and Mail. Other than that, we mainly have Eclipse produced APIs for Jakarta. I'm not sure if we want to migrate our Geronimo Specs jars or use the stock Jakarta APIs. Important note, if we do, we may not need the jakartaee-api because there is already a Uber jar for Jakarta within the different profiles. Should we get our user to use it as provided. And on our side, should we create just a bom in our project and get the job done? Some APIs are also more or less implementations and vice versa. This is the case for mail, faces, and some more as you mentioned. I'm fine including Mail provider + Geronimo Mail spec in the jakartaee-api jar but mind that in the past some users wanted to use Sun implementation and it will be harder D/ what about inconsistencies like ... Some implementations can be switched, for example Faces. Which is also a mess because API and IMPL are linked together. I had previously the Faces API but of course you need the implementation as well, same as for mail. But Plume uses Mojorra. So we are in the situation where we need to pick one or the other. B/ or this alternative ... Tomcat classifier because we don't want to cheap with APIs already provided in Tomcat with the risk of not being fully aligned. So we use Tomcat APIs. Should we go the way around and remove Tomcat APIs from the final distribution and get rid of the Tomcat classifier? Note sure if my reply is clear, hopefully it helps. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Thu, May 26, 2022 at 3:23 AM David Blevins wrote: > Thanks so much for this. I even started creating one myself early this > morning, ... then the rest of the day happened LOL > > > On May 25, 2022, at 1:56 PM, Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > > > > Here it is > > > https://gist.github.com/jeanouii/9bb6c14bdde227e2fed83fd73db3a646/revisions > > Looks like we've yanked out Faces, JSTL, Mail, etc. I suspect we're > trying to hit the line of not including APIs that are implementations. The > real trick is even HttpServlet is completely dependent on the servlet > container in the same way Faces, Mail, JSTL, etc are dependent on their > implementations. I'm not too sure if Activation is also considered an > implementation as well -- I'm not sure off-hand if there is a separate > implementation jar. > > I know we didn't include mail in our javaee-api jar, so excluding is > following that logic. I also know we have the > jakartaee-api-9.1-M2-SNAPSHOT-tomcat.jar, which cuts out everything very > close to the way we've now done it in jakartaee-api-9.1-M2-SNAPSHOT.jar > > How do we want to handle this? > > Seems our options are: > > A. Leave jakartaee-api-X.jar and jakartaee-api-X-tomcat.jar nearly > identical in missing many specs. There is no uber jar people can compile > against that has most everything. People would need to discover which > specs are missing and pull them in individually. > > B. Eliminate having two jars, there is now just > jakartaee-api-X-tomcat.jar (which we call jakartaee-api-X.jar). There is > no uber jar people can compile against that has most everything. People > would need to discover which specs are missing and pull them in > individually. > > C. Do what we did with javaee-api.jar and leave mail out while including > other impls. There is something close to an uber, but still not quite as > identical to the jakartaee-api jar produced at Eclipse using the Eclipse > impls. > > D. Reverse our stance on the mail thing. There would be jakartaee-api > that contained everything including mail and it would be identical to the > jakartaee-api jar produced at Eclipse using the Eclipse impls. > > Not sure where I sit on this spectrum yet, throwing it out so we all can > think in parallel. > > Is it at all possible to get a similar diff for the "-tomcat" jar? > > > -David > >
Re: TomEE 9.x - from javax to jakarta namespace
Thanks so much for this. I even started creating one myself early this morning, ... then the rest of the day happened LOL > On May 25, 2022, at 1:56 PM, Jean-Louis Monteiro > wrote: > > Here it is > https://gist.github.com/jeanouii/9bb6c14bdde227e2fed83fd73db3a646/revisions Looks like we've yanked out Faces, JSTL, Mail, etc. I suspect we're trying to hit the line of not including APIs that are implementations. The real trick is even HttpServlet is completely dependent on the servlet container in the same way Faces, Mail, JSTL, etc are dependent on their implementations. I'm not too sure if Activation is also considered an implementation as well -- I'm not sure off-hand if there is a separate implementation jar. I know we didn't include mail in our javaee-api jar, so excluding is following that logic. I also know we have the jakartaee-api-9.1-M2-SNAPSHOT-tomcat.jar, which cuts out everything very close to the way we've now done it in jakartaee-api-9.1-M2-SNAPSHOT.jar How do we want to handle this? Seems our options are: A. Leave jakartaee-api-X.jar and jakartaee-api-X-tomcat.jar nearly identical in missing many specs. There is no uber jar people can compile against that has most everything. People would need to discover which specs are missing and pull them in individually. B. Eliminate having two jars, there is now just jakartaee-api-X-tomcat.jar (which we call jakartaee-api-X.jar). There is no uber jar people can compile against that has most everything. People would need to discover which specs are missing and pull them in individually. C. Do what we did with javaee-api.jar and leave mail out while including other impls. There is something close to an uber, but still not quite as identical to the jakartaee-api jar produced at Eclipse using the Eclipse impls. D. Reverse our stance on the mail thing. There would be jakartaee-api that contained everything including mail and it would be identical to the jakartaee-api jar produced at Eclipse using the Eclipse impls. Not sure where I sit on this spectrum yet, throwing it out so we all can think in parallel. Is it at all possible to get a similar diff for the "-tomcat" jar? -David smime.p7s Description: S/MIME cryptographic signature
Re: TomEE 9.x - from javax to jakarta namespace
Here it is https://gist.github.com/jeanouii/9bb6c14bdde227e2fed83fd73db3a646/revisions -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Wed, May 25, 2022 at 1:10 PM Jean-Louis Monteiro < jlmonte...@tomitribe.com> wrote: > Ah ok, thanks, it wasn't clear :-) > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Wed, May 25, 2022 at 1:09 PM Zowalla, Richard < > richard.zowa...@hs-heilbronn.de> wrote: > >> Guess it is: >> >> jakarataee-api-9.1-M2-SNAPSHOT-tomcat.jar vs jakarataee-api-9.1-M1- >> tomcat.jar >> >> (similar to javaee-api differences in the gist) >> >> >> Am Mittwoch, dem 25.05.2022 um 12:21 +0200 schrieb Jean-Louis Monteiro: >> > Hey David, >> > >> > Does not seem to be undoable. >> > >> > Just a quick question: do you want the diff between jakartaee-api and >> > javaee-api or do you want diff between every version of the >> > jakartaee-api? >> > >> > -- >> > Jean-Louis Monteiro >> > http://twitter.com/jlouismonteiro >> > http://www.tomitribe.com >> > >> > >> > On Wed, May 25, 2022 at 2:44 AM David Blevins < >> > david.blev...@gmail.com> >> > wrote: >> > >> > > I haven't had a chance to dig into the differences on the >> > > jakartaee-api >> > > jars like I did for the javaee-api jars. Is it at all possible you >> > > could >> > > create a diff like this one? >> > > >> > > - >> > > >> https://gist.github.com/dblevins/7535757fb8eceb51ed30ae9b705f9cbf/revisions >> > > >> > > I basically built each, did a `jar tvf javaee-api-8.0-5.jar | cut >> > > -c 37-` >> > > and pasted that output into a gist, then did it again against the >> > > javaee-api-8.0-6.jar and updated the content in the gist. >> > > >> > > It'd be super helpful. >> > > >> > > I did look at the commits, but with maven transitive deps and such >> > > I don't >> > > really trust myself to eyeball it correctly. >> > > >> > > >> > > -David >> > > >> > > >> > > > On May 24, 2022, at 6:44 AM, Jean-Louis Monteiro < >> > > jlmonte...@tomitribe.com> wrote: >> > > > Alright, time for a new update. >> > > > >> > > > TomEE 8.x with JDK8 and EE8 is equivalent to TomEE 9.x with >> > > > JDK11/JDK17 >> > > and >> > > > EE9. >> > > > The build is still not full green, but it's time to start >> > > > grabbing user >> > > > feedback as we discussed. >> > > > >> > > > So the work started to take every single piece we fixed or >> > > > patched to >> > > start >> > > > doing releases and if possible run TCK + signature Tests. >> > > > >> > > > David did activation and mail milestones. Richard used the >> > > > milestone to >> > > fix >> > > > and we are now under vote for activation 2.0 final and Richard is >> > > > making >> > > > some awesomeness on the mail spec and impl. We should be able to >> > > > get >> > > final >> > > > versions soon. >> > > > >> > > > We also have an OWB vote starting today for a jakarta compatible >> > > > version >> > > > (including TCK). >> > > > Next step is to release a milestone for jakartaee-api 9.1-M2 and >> > > > move on. >> > > > >> > > > >> > > > >> > > > -- >> > > > Jean-Louis Monteiro >> > > > http://twitter.com/jlouismonteiro >> > > > http://www.tomitribe.com >> > > > >> > > > >> > > > On Thu, May 12, 2022 at 9:29 AM Wiesner, Martin < >> > > > martin.wies...@hs-heilbronn.de> wrote: >> > > > >> > > > > +1 >> > > > > >> > > > > Best >> > > > > Martin >> > > > > — >> > > > > https://twitter.com/mawiesne >> > > > > >> > > > > >> > > > > Am 11.05.2022 um 19:00 schrieb Cesar Hernandez < >> > > > > cesargu...@gmail.com >> > > > > <
Re: TomEE 9.x - from javax to jakarta namespace
Ah ok, thanks, it wasn't clear :-) -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Wed, May 25, 2022 at 1:09 PM Zowalla, Richard < richard.zowa...@hs-heilbronn.de> wrote: > Guess it is: > > jakarataee-api-9.1-M2-SNAPSHOT-tomcat.jar vs jakarataee-api-9.1-M1- > tomcat.jar > > (similar to javaee-api differences in the gist) > > > Am Mittwoch, dem 25.05.2022 um 12:21 +0200 schrieb Jean-Louis Monteiro: > > Hey David, > > > > Does not seem to be undoable. > > > > Just a quick question: do you want the diff between jakartaee-api and > > javaee-api or do you want diff between every version of the > > jakartaee-api? > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Wed, May 25, 2022 at 2:44 AM David Blevins < > > david.blev...@gmail.com> > > wrote: > > > > > I haven't had a chance to dig into the differences on the > > > jakartaee-api > > > jars like I did for the javaee-api jars. Is it at all possible you > > > could > > > create a diff like this one? > > > > > > - > > > > https://gist.github.com/dblevins/7535757fb8eceb51ed30ae9b705f9cbf/revisions > > > > > > I basically built each, did a `jar tvf javaee-api-8.0-5.jar | cut > > > -c 37-` > > > and pasted that output into a gist, then did it again against the > > > javaee-api-8.0-6.jar and updated the content in the gist. > > > > > > It'd be super helpful. > > > > > > I did look at the commits, but with maven transitive deps and such > > > I don't > > > really trust myself to eyeball it correctly. > > > > > > > > > -David > > > > > > > > > > On May 24, 2022, at 6:44 AM, Jean-Louis Monteiro < > > > jlmonte...@tomitribe.com> wrote: > > > > Alright, time for a new update. > > > > > > > > TomEE 8.x with JDK8 and EE8 is equivalent to TomEE 9.x with > > > > JDK11/JDK17 > > > and > > > > EE9. > > > > The build is still not full green, but it's time to start > > > > grabbing user > > > > feedback as we discussed. > > > > > > > > So the work started to take every single piece we fixed or > > > > patched to > > > start > > > > doing releases and if possible run TCK + signature Tests. > > > > > > > > David did activation and mail milestones. Richard used the > > > > milestone to > > > fix > > > > and we are now under vote for activation 2.0 final and Richard is > > > > making > > > > some awesomeness on the mail spec and impl. We should be able to > > > > get > > > final > > > > versions soon. > > > > > > > > We also have an OWB vote starting today for a jakarta compatible > > > > version > > > > (including TCK). > > > > Next step is to release a milestone for jakartaee-api 9.1-M2 and > > > > move on. > > > > > > > > > > > > > > > > -- > > > > Jean-Louis Monteiro > > > > http://twitter.com/jlouismonteiro > > > > http://www.tomitribe.com > > > > > > > > > > > > On Thu, May 12, 2022 at 9:29 AM Wiesner, Martin < > > > > martin.wies...@hs-heilbronn.de> wrote: > > > > > > > > > +1 > > > > > > > > > > Best > > > > > Martin > > > > > — > > > > > https://twitter.com/mawiesne > > > > > > > > > > > > > > > Am 11.05.2022 um 19:00 schrieb Cesar Hernandez < > > > > > cesargu...@gmail.com > > > > > <mailto:cesargu...@gmail.com>>: > > > > > > > > > > +1, Thank you! > > > > > > > > > > > > > > > El mié, 11 may 2022 a las 9:06, Daniel Dias Dos Santos (< > > > > > daniel.dias.analist...@gmail.com > > daniel.dias.analist...@gmail.com>>) > > > > > escribió: > > > > > > > > > > +1 > > > > > > > > > > On Wed, May 11, 2022, 12:00 Zowalla, Richard < > > > > > richard.zowa...@hs-heilbronn.de > > > > richard.zowa...@hs-heilbronn.de > > > > > > > > > > wrote: > > > > > > > > > >
Re: TomEE 9.x - from javax to jakarta namespace
Guess it is: jakarataee-api-9.1-M2-SNAPSHOT-tomcat.jar vs jakarataee-api-9.1-M1- tomcat.jar (similar to javaee-api differences in the gist) Am Mittwoch, dem 25.05.2022 um 12:21 +0200 schrieb Jean-Louis Monteiro: > Hey David, > > Does not seem to be undoable. > > Just a quick question: do you want the diff between jakartaee-api and > javaee-api or do you want diff between every version of the > jakartaee-api? > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Wed, May 25, 2022 at 2:44 AM David Blevins < > david.blev...@gmail.com> > wrote: > > > I haven't had a chance to dig into the differences on the > > jakartaee-api > > jars like I did for the javaee-api jars. Is it at all possible you > > could > > create a diff like this one? > > > > - > > https://gist.github.com/dblevins/7535757fb8eceb51ed30ae9b705f9cbf/revisions > > > > I basically built each, did a `jar tvf javaee-api-8.0-5.jar | cut > > -c 37-` > > and pasted that output into a gist, then did it again against the > > javaee-api-8.0-6.jar and updated the content in the gist. > > > > It'd be super helpful. > > > > I did look at the commits, but with maven transitive deps and such > > I don't > > really trust myself to eyeball it correctly. > > > > > > -David > > > > > > > On May 24, 2022, at 6:44 AM, Jean-Louis Monteiro < > > jlmonte...@tomitribe.com> wrote: > > > Alright, time for a new update. > > > > > > TomEE 8.x with JDK8 and EE8 is equivalent to TomEE 9.x with > > > JDK11/JDK17 > > and > > > EE9. > > > The build is still not full green, but it's time to start > > > grabbing user > > > feedback as we discussed. > > > > > > So the work started to take every single piece we fixed or > > > patched to > > start > > > doing releases and if possible run TCK + signature Tests. > > > > > > David did activation and mail milestones. Richard used the > > > milestone to > > fix > > > and we are now under vote for activation 2.0 final and Richard is > > > making > > > some awesomeness on the mail spec and impl. We should be able to > > > get > > final > > > versions soon. > > > > > > We also have an OWB vote starting today for a jakarta compatible > > > version > > > (including TCK). > > > Next step is to release a milestone for jakartaee-api 9.1-M2 and > > > move on. > > > > > > > > > > > > -- > > > Jean-Louis Monteiro > > > http://twitter.com/jlouismonteiro > > > http://www.tomitribe.com > > > > > > > > > On Thu, May 12, 2022 at 9:29 AM Wiesner, Martin < > > > martin.wies...@hs-heilbronn.de> wrote: > > > > > > > +1 > > > > > > > > Best > > > > Martin > > > > — > > > > https://twitter.com/mawiesne > > > > > > > > > > > > Am 11.05.2022 um 19:00 schrieb Cesar Hernandez < > > > > cesargu...@gmail.com > > > > <mailto:cesargu...@gmail.com>>: > > > > > > > > +1, Thank you! > > > > > > > > > > > > El mié, 11 may 2022 a las 9:06, Daniel Dias Dos Santos (< > > > > daniel.dias.analist...@gmail.com > daniel.dias.analist...@gmail.com>>) > > > > escribió: > > > > > > > > +1 > > > > > > > > On Wed, May 11, 2022, 12:00 Zowalla, Richard < > > > > richard.zowa...@hs-heilbronn.de > > > richard.zowa...@hs-heilbronn.de > > > > > > > > wrote: > > > > > > > > I am fine with it: +1 > > > > > > > > Von: Jean-Louis Monteiro > > > jlmonte...@tomitribe.com>> > > > > Gesendet: Mittwoch, 11. Mai 2022 15:57:54 > > > > An: dev@tomee.apache.org<mailto:dev@tomee.apache.org> > > > > Betreff: Re: TomEE 9.x - from javax to jakarta namespace > > > > > > > > Alright, with the latest changes pushed yesterday and today, we > > > > are now > > > > at > > > > the exact same numbers for TomEE 8.x / Jakarta EE 8 under JDK8 > > > > and TomEE > > > > 9.x / Jakarta 9.1 under JDK17. > > > > > > > > If everyone is ok with it, we can create a new
Re: TomEE 9.x - from javax to jakarta namespace
Hey David, Does not seem to be undoable. Just a quick question: do you want the diff between jakartaee-api and javaee-api or do you want diff between every version of the jakartaee-api? -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Wed, May 25, 2022 at 2:44 AM David Blevins wrote: > I haven't had a chance to dig into the differences on the jakartaee-api > jars like I did for the javaee-api jars. Is it at all possible you could > create a diff like this one? > > - > https://gist.github.com/dblevins/7535757fb8eceb51ed30ae9b705f9cbf/revisions > > I basically built each, did a `jar tvf javaee-api-8.0-5.jar | cut -c 37-` > and pasted that output into a gist, then did it again against the > javaee-api-8.0-6.jar and updated the content in the gist. > > It'd be super helpful. > > I did look at the commits, but with maven transitive deps and such I don't > really trust myself to eyeball it correctly. > > > -David > > > > On May 24, 2022, at 6:44 AM, Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > > > > Alright, time for a new update. > > > > TomEE 8.x with JDK8 and EE8 is equivalent to TomEE 9.x with JDK11/JDK17 > and > > EE9. > > The build is still not full green, but it's time to start grabbing user > > feedback as we discussed. > > > > So the work started to take every single piece we fixed or patched to > start > > doing releases and if possible run TCK + signature Tests. > > > > David did activation and mail milestones. Richard used the milestone to > fix > > and we are now under vote for activation 2.0 final and Richard is making > > some awesomeness on the mail spec and impl. We should be able to get > final > > versions soon. > > > > We also have an OWB vote starting today for a jakarta compatible version > > (including TCK). > > Next step is to release a milestone for jakartaee-api 9.1-M2 and move on. > > > > > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Thu, May 12, 2022 at 9:29 AM Wiesner, Martin < > > martin.wies...@hs-heilbronn.de> wrote: > > > >> +1 > >> > >> Best > >> Martin > >> — > >> https://twitter.com/mawiesne > >> > >> > >> Am 11.05.2022 um 19:00 schrieb Cesar Hernandez >> <mailto:cesargu...@gmail.com>>: > >> > >> +1, Thank you! > >> > >> > >> El mié, 11 may 2022 a las 9:06, Daniel Dias Dos Santos (< > >> daniel.dias.analist...@gmail.com daniel.dias.analist...@gmail.com>>) > >> escribió: > >> > >> +1 > >> > >> On Wed, May 11, 2022, 12:00 Zowalla, Richard < > >> richard.zowa...@hs-heilbronn.de<mailto:richard.zowa...@hs-heilbronn.de > >> > >> wrote: > >> > >> I am fine with it: +1 > >> > >> Von: Jean-Louis Monteiro >> jlmonte...@tomitribe.com>> > >> Gesendet: Mittwoch, 11. Mai 2022 15:57:54 > >> An: dev@tomee.apache.org<mailto:dev@tomee.apache.org> > >> Betreff: Re: TomEE 9.x - from javax to jakarta namespace > >> > >> Alright, with the latest changes pushed yesterday and today, we are now > >> at > >> the exact same numbers for TomEE 8.x / Jakarta EE 8 under JDK8 and TomEE > >> 9.x / Jakarta 9.1 under JDK17. > >> > >> If everyone is ok with it, we can create a new milestone and give users > >> the > >> opportunity to provide us with some feedback and to report bugs. > >> > >> -- > >> Jean-Louis Monteiro > >> http://twitter.com/jlouismonteiro > >> http://www.tomitribe.com > >> > >> > >> On Tue, May 10, 2022 at 7:06 PM David Blevins > >> wrote: > >> > >> Was checking out the TCK numbers this morning can make to suggest a > >> 9.0.0-M8 while things look good and found this amazing email. > >> > >> The 9.0.x branch is looking absolutely amazing!!! > >> > >> What do we think about pushing out a 9.0.0-M8 while things are in their > >> peak-stable state? I'm sure we'll have to rip up a few more things to > >> finish off the remaining Jakarta EE and MP TCK issues. Would be great > >> to > >> have something that isn't M7 to fallback on as a reference point to > >> track > >> regressions. > >> > >> Thoughts? > >> > >> > >> -David >
Re: TomEE 9.x - from javax to jakarta namespace
Am Mittwoch, dem 25.05.2022 um 02:28 +0200 schrieb Jean-Louis Monteiro: > For 2/ I can help you tomorrow if you want/need. Would be very much appreciated to get a second pair of eyes. Gruß Richard smime.p7s Description: S/MIME cryptographic signature
Re: TomEE 9.x - from javax to jakarta namespace
I haven't had a chance to dig into the differences on the jakartaee-api jars like I did for the javaee-api jars. Is it at all possible you could create a diff like this one? - https://gist.github.com/dblevins/7535757fb8eceb51ed30ae9b705f9cbf/revisions I basically built each, did a `jar tvf javaee-api-8.0-5.jar | cut -c 37-` and pasted that output into a gist, then did it again against the javaee-api-8.0-6.jar and updated the content in the gist. It'd be super helpful. I did look at the commits, but with maven transitive deps and such I don't really trust myself to eyeball it correctly. -David > On May 24, 2022, at 6:44 AM, Jean-Louis Monteiro > wrote: > > Alright, time for a new update. > > TomEE 8.x with JDK8 and EE8 is equivalent to TomEE 9.x with JDK11/JDK17 and > EE9. > The build is still not full green, but it's time to start grabbing user > feedback as we discussed. > > So the work started to take every single piece we fixed or patched to start > doing releases and if possible run TCK + signature Tests. > > David did activation and mail milestones. Richard used the milestone to fix > and we are now under vote for activation 2.0 final and Richard is making > some awesomeness on the mail spec and impl. We should be able to get final > versions soon. > > We also have an OWB vote starting today for a jakarta compatible version > (including TCK). > Next step is to release a milestone for jakartaee-api 9.1-M2 and move on. > > > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Thu, May 12, 2022 at 9:29 AM Wiesner, Martin < > martin.wies...@hs-heilbronn.de> wrote: > >> +1 >> >> Best >> Martin >> — >> https://twitter.com/mawiesne >> >> >> Am 11.05.2022 um 19:00 schrieb Cesar Hernandez > <mailto:cesargu...@gmail.com>>: >> >> +1, Thank you! >> >> >> El mié, 11 may 2022 a las 9:06, Daniel Dias Dos Santos (< >> daniel.dias.analist...@gmail.com<mailto:daniel.dias.analist...@gmail.com>>) >> escribió: >> >> +1 >> >> On Wed, May 11, 2022, 12:00 Zowalla, Richard < >> richard.zowa...@hs-heilbronn.de<mailto:richard.zowa...@hs-heilbronn.de>> >> wrote: >> >> I am fine with it: +1 >> >> Von: Jean-Louis Monteiro > jlmonte...@tomitribe.com>> >> Gesendet: Mittwoch, 11. Mai 2022 15:57:54 >> An: dev@tomee.apache.org<mailto:dev@tomee.apache.org> >> Betreff: Re: TomEE 9.x - from javax to jakarta namespace >> >> Alright, with the latest changes pushed yesterday and today, we are now >> at >> the exact same numbers for TomEE 8.x / Jakarta EE 8 under JDK8 and TomEE >> 9.x / Jakarta 9.1 under JDK17. >> >> If everyone is ok with it, we can create a new milestone and give users >> the >> opportunity to provide us with some feedback and to report bugs. >> >> -- >> Jean-Louis Monteiro >> http://twitter.com/jlouismonteiro >> http://www.tomitribe.com >> >> >> On Tue, May 10, 2022 at 7:06 PM David Blevins >> wrote: >> >> Was checking out the TCK numbers this morning can make to suggest a >> 9.0.0-M8 while things look good and found this amazing email. >> >> The 9.0.x branch is looking absolutely amazing!!! >> >> What do we think about pushing out a 9.0.0-M8 while things are in their >> peak-stable state? I'm sure we'll have to rip up a few more things to >> finish off the remaining Jakarta EE and MP TCK issues. Would be great >> to >> have something that isn't M7 to fallback on as a reference point to >> track >> regressions. >> >> Thoughts? >> >> >> -David >> >> >> >> On May 10, 2022, at 3:56 AM, Jean-Louis Monteiro < >> jlmonte...@tomitribe.com<mailto:jlmonte...@tomitribe.com>> wrote: >> >> Hi all, >> >> Time for some reporting >> >> On our journey to migrate TomEE over from javax to jakarta namespace, >> we >> had many issues. >> After updating all our code, we had to do a bunch of dependency >> upgrades >> after upgrading many of them (OpenWebbeans, BVal, Geronimo, etc). >> >> We then faced many issues with non compatible libraries for example >> (ActiveMQ, commons-dbcp, CXF, sxc, taglib, etc). So we ended up >> repacking >> them in our own groupId after using the Maven Shade plugin to >> relocate >> the >> packages. >> >> We worked on BVal TCK and CDI TCK and we are close to passing the
Re: TomEE 9.x - from javax to jakarta namespace
Thanks for the detailed status Richard. For 1/ I sent my opinion. The vote is outgoing and I'd keep the fix you did for now without any "cheap" system properties. I'm not a big big fan and it's a major release. So I'd go lazy instead of eager on this one and see if really it's harmful or not. For 2/ I can help you tomorrow if you want/need. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, May 24, 2022 at 7:14 PM Zowalla, Richard < richard.zowa...@hs-heilbronn.de> wrote: > To give a more detailed view / update from the spec tck party regarding > activation and mail: > > (A) Geronimo Activation 2.0 > > After a first milestone (M1) and some additional fixes after running > the activation TCK [1] and related signatures tests, we are now passing > them. > > JL prepared a release artifact (1.0.0), which is currently under vote. > > During the tck work, we found some inconsistency / unspecified > behaviour of "normalizeMimeTypeParameter" of ActivationDataFlavor. > While this method is tested in the TCK on the basis of the reference > implementation neither the spec itself nor the javadoc are really clear > about the "right" return value. At the moment, we adjusted it to pass > the TCK test in question. > > There is an ongoing discussion at dev@geronimo if this is a desired > behaviour or if a system property should be introduced in order to > reduce the possibility of breaking some users. > > (B) Geronimo Mail 2.0 / 2.1 > > The current mail impl has some TCK failures. It seems, that we need to > do some additional work to get it compliant with the standalone mail > tck [3]. > > The signature tests are failing for Java 11 but are fine with Java 8 > [4] due to some usage of Object#finalize() and missing annotations > (only available in Java 9+) in the Geronimo implementation. While it is > not that important for EE9, we need to keep it in mind for EE10. > > We currently pass 166 out of 321 mail tck tests [5]. I guess, we need > to give it some more love to get the numbers up and finally get it to > pass the mail tck. The good thing is, that we already pass the javamail > tests for TomEE [6]. > > Gruß > Richard > > > > [1] https://jakarta.ee/specifications/activation/2.0/ > [2] https://lists.apache.org/thread/h8twm4rmdxt67fx227nyywjp96b6cky1 > [3] https://jakarta.ee/specifications/mail/2.0/ > [4] https://issues.apache.org/jira/browse/GERONIMO-6834 > [5] https://issues.apache.org/jira/browse/GERONIMO-6835 > [6] > > https://tck.work/tomee/tests?build=1651841331620=com.sun.ts.tests.javamail > > Am Dienstag, dem 24.05.2022 um 15:44 +0200 schrieb Jean-Louis Monteiro: > > Alright, time for a new update. > > > > TomEE 8.x with JDK8 and EE8 is equivalent to TomEE 9.x with > > JDK11/JDK17 and > > EE9. > > The build is still not full green, but it's time to start grabbing > > user > > feedback as we discussed. > > > > So the work started to take every single piece we fixed or patched to > > start > > doing releases and if possible run TCK + signature Tests. > > > > David did activation and mail milestones. Richard used the milestone > > to fix > > and we are now under vote for activation 2.0 final and Richard is > > making > > some awesomeness on the mail spec and impl. We should be able to get > > final > > versions soon. > > > > We also have an OWB vote starting today for a jakarta compatible > > version > > (including TCK). > > Next step is to release a milestone for jakartaee-api 9.1-M2 and move > > on. > > > > > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Thu, May 12, 2022 at 9:29 AM Wiesner, Martin < > > martin.wies...@hs-heilbronn.de> wrote: > > > > > +1 > > > > > > Best > > > Martin > > > — > > > https://twitter.com/mawiesne > > > > > > > > > Am 11.05.2022 um 19:00 schrieb Cesar Hernandez < > > > cesargu...@gmail.com > > > <mailto:cesargu...@gmail.com>>: > > > > > > +1, Thank you! > > > > > > > > > El mié, 11 may 2022 a las 9:06, Daniel Dias Dos Santos (< > > > daniel.dias.analist...@gmail.com > > daniel.dias.analist...@gmail.com>>) > > > escribió: > > > > > > +1 > > > > > > On Wed, May 11, 2022, 12:00 Zowalla, Richard < > > > richard.zowa...@hs-heilbronn.de > > richard.zowa...@hs-heilbronn.de>> > > > wrote: > >
Jakarta Mail TCK - Additional Thoughts? (was: TomEE 9.x - from javax to jakarta namespace)
t; on. > > > > > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Thu, May 12, 2022 at 9:29 AM Wiesner, Martin < > > martin.wies...@hs-heilbronn.de> wrote: > > > > > +1 > > > > > > Best > > > Martin > > > — > > > https://twitter.com/mawiesne > > > > > > > > > Am 11.05.2022 um 19:00 schrieb Cesar Hernandez < > > > cesargu...@gmail.com > > > <mailto:cesargu...@gmail.com>>: > > > > > > +1, Thank you! > > > > > > > > > El mié, 11 may 2022 a las 9:06, Daniel Dias Dos Santos (< > > > daniel.dias.analist...@gmail.com > > daniel.dias.analist...@gmail.com>>) > > > escribió: > > > > > > +1 > > > > > > On Wed, May 11, 2022, 12:00 Zowalla, Richard < > > > richard.zowa...@hs-heilbronn.de > > richard.zowa...@hs-heilbronn.de>> > > > wrote: > > > > > > I am fine with it: +1 > > > > > > Von: Jean-Louis Monteiro > > jlmonte...@tomitribe.com>> > > > Gesendet: Mittwoch, 11. Mai 2022 15:57:54 > > > An: dev@tomee.apache.org<mailto:dev@tomee.apache.org> > > > Betreff: Re: TomEE 9.x - from javax to jakarta namespace > > > > > > Alright, with the latest changes pushed yesterday and today, we > > > are > > > now > > > at > > > the exact same numbers for TomEE 8.x / Jakarta EE 8 under JDK8 > > > and > > > TomEE > > > 9.x / Jakarta 9.1 under JDK17. > > > > > > If everyone is ok with it, we can create a new milestone and give > > > users > > > the > > > opportunity to provide us with some feedback and to report bugs. > > > > > > -- > > > Jean-Louis Monteiro > > > http://twitter.com/jlouismonteiro > > > http://www.tomitribe.com > > > > > > > > > On Tue, May 10, 2022 at 7:06 PM David Blevins < > > > david.blev...@gmail.com> > > > wrote: > > > > > > Was checking out the TCK numbers this morning can make to suggest > > > a > > > 9.0.0-M8 while things look good and found this amazing email. > > > > > > The 9.0.x branch is looking absolutely amazing!!! > > > > > > What do we think about pushing out a 9.0.0-M8 while things are in > > > their > > > peak-stable state? I'm sure we'll have to rip up a few more > > > things > > > to > > > finish off the remaining Jakarta EE and MP TCK issues. Would be > > > great > > > to > > > have something that isn't M7 to fallback on as a reference point > > > to > > > track > > > regressions. > > > > > > Thoughts? > > > > > > > > > -David > > > > > > > > > > > > On May 10, 2022, at 3:56 AM, Jean-Louis Monteiro < > > > jlmonte...@tomitribe.com<mailto:jlmonte...@tomitribe.com>> wrote: > > > > > > Hi all, > > > > > > Time for some reporting > > > > > > On our journey to migrate TomEE over from javax to jakarta > > > namespace, > > > we > > > had many issues. > > > After updating all our code, we had to do a bunch of dependency > > > upgrades > > > after upgrading many of them (OpenWebbeans, BVal, Geronimo, etc). > > > > > > We then faced many issues with non compatible libraries for > > > example > > > (ActiveMQ, commons-dbcp, CXF, sxc, taglib, etc). So we ended up > > > repacking > > > them in our own groupId after using the Maven Shade plugin to > > > relocate > > > the > > > packages. > > > > > > We worked on BVal TCK and CDI TCK and we are close to passing > > > them. > > > > > > But we had before to solve all our outdated MicroProfile 1.3 > > > stack > > > to > > > the > > > most recent and jakarta compatible version. Geronimo > > > implementations > > > being > > > far being, we decided to use some SmallRye implementations until > > > we > > > can > > > dedicate some time to update our Apache implementations (config, > > > metrics, > > > health, openapi, opentracing, fault tolerance). > > > > > > Our build is now more stable, but still not
Re: TomEE 9.x - from javax to jakarta namespace
To give a more detailed view / update from the spec tck party regarding activation and mail: (A) Geronimo Activation 2.0 After a first milestone (M1) and some additional fixes after running the activation TCK [1] and related signatures tests, we are now passing them. JL prepared a release artifact (1.0.0), which is currently under vote. During the tck work, we found some inconsistency / unspecified behaviour of "normalizeMimeTypeParameter" of ActivationDataFlavor. While this method is tested in the TCK on the basis of the reference implementation neither the spec itself nor the javadoc are really clear about the "right" return value. At the moment, we adjusted it to pass the TCK test in question. There is an ongoing discussion at dev@geronimo if this is a desired behaviour or if a system property should be introduced in order to reduce the possibility of breaking some users. (B) Geronimo Mail 2.0 / 2.1 The current mail impl has some TCK failures. It seems, that we need to do some additional work to get it compliant with the standalone mail tck [3]. The signature tests are failing for Java 11 but are fine with Java 8 [4] due to some usage of Object#finalize() and missing annotations (only available in Java 9+) in the Geronimo implementation. While it is not that important for EE9, we need to keep it in mind for EE10. We currently pass 166 out of 321 mail tck tests [5]. I guess, we need to give it some more love to get the numbers up and finally get it to pass the mail tck. The good thing is, that we already pass the javamail tests for TomEE [6]. Gruß Richard [1] https://jakarta.ee/specifications/activation/2.0/ [2] https://lists.apache.org/thread/h8twm4rmdxt67fx227nyywjp96b6cky1 [3] https://jakarta.ee/specifications/mail/2.0/ [4] https://issues.apache.org/jira/browse/GERONIMO-6834 [5] https://issues.apache.org/jira/browse/GERONIMO-6835 [6] https://tck.work/tomee/tests?build=1651841331620=com.sun.ts.tests.javamail Am Dienstag, dem 24.05.2022 um 15:44 +0200 schrieb Jean-Louis Monteiro: > Alright, time for a new update. > > TomEE 8.x with JDK8 and EE8 is equivalent to TomEE 9.x with > JDK11/JDK17 and > EE9. > The build is still not full green, but it's time to start grabbing > user > feedback as we discussed. > > So the work started to take every single piece we fixed or patched to > start > doing releases and if possible run TCK + signature Tests. > > David did activation and mail milestones. Richard used the milestone > to fix > and we are now under vote for activation 2.0 final and Richard is > making > some awesomeness on the mail spec and impl. We should be able to get > final > versions soon. > > We also have an OWB vote starting today for a jakarta compatible > version > (including TCK). > Next step is to release a milestone for jakartaee-api 9.1-M2 and move > on. > > > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Thu, May 12, 2022 at 9:29 AM Wiesner, Martin < > martin.wies...@hs-heilbronn.de> wrote: > > > +1 > > > > Best > > Martin > > — > > https://twitter.com/mawiesne > > > > > > Am 11.05.2022 um 19:00 schrieb Cesar Hernandez < > > cesargu...@gmail.com > > <mailto:cesargu...@gmail.com>>: > > > > +1, Thank you! > > > > > > El mié, 11 may 2022 a las 9:06, Daniel Dias Dos Santos (< > > daniel.dias.analist...@gmail.com > daniel.dias.analist...@gmail.com>>) > > escribió: > > > > +1 > > > > On Wed, May 11, 2022, 12:00 Zowalla, Richard < > > richard.zowa...@hs-heilbronn.de > richard.zowa...@hs-heilbronn.de>> > > wrote: > > > > I am fine with it: +1 > > > > Von: Jean-Louis Monteiro > jlmonte...@tomitribe.com>> > > Gesendet: Mittwoch, 11. Mai 2022 15:57:54 > > An: dev@tomee.apache.org<mailto:dev@tomee.apache.org> > > Betreff: Re: TomEE 9.x - from javax to jakarta namespace > > > > Alright, with the latest changes pushed yesterday and today, we are > > now > > at > > the exact same numbers for TomEE 8.x / Jakarta EE 8 under JDK8 and > > TomEE > > 9.x / Jakarta 9.1 under JDK17. > > > > If everyone is ok with it, we can create a new milestone and give > > users > > the > > opportunity to provide us with some feedback and to report bugs. > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Tue, May 10, 2022 at 7:06 PM David Blevins < > > david.blev...@gmail.com> > > wrote: > > > > Was checking
Re: TomEE 9.x - from javax to jakarta namespace
Alright, time for a new update. TomEE 8.x with JDK8 and EE8 is equivalent to TomEE 9.x with JDK11/JDK17 and EE9. The build is still not full green, but it's time to start grabbing user feedback as we discussed. So the work started to take every single piece we fixed or patched to start doing releases and if possible run TCK + signature Tests. David did activation and mail milestones. Richard used the milestone to fix and we are now under vote for activation 2.0 final and Richard is making some awesomeness on the mail spec and impl. We should be able to get final versions soon. We also have an OWB vote starting today for a jakarta compatible version (including TCK). Next step is to release a milestone for jakartaee-api 9.1-M2 and move on. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Thu, May 12, 2022 at 9:29 AM Wiesner, Martin < martin.wies...@hs-heilbronn.de> wrote: > +1 > > Best > Martin > — > https://twitter.com/mawiesne > > > Am 11.05.2022 um 19:00 schrieb Cesar Hernandez <mailto:cesargu...@gmail.com>>: > > +1, Thank you! > > > El mié, 11 may 2022 a las 9:06, Daniel Dias Dos Santos (< > daniel.dias.analist...@gmail.com<mailto:daniel.dias.analist...@gmail.com>>) > escribió: > > +1 > > On Wed, May 11, 2022, 12:00 Zowalla, Richard < > richard.zowa...@hs-heilbronn.de<mailto:richard.zowa...@hs-heilbronn.de>> > wrote: > > I am fine with it: +1 > > Von: Jean-Louis Monteiro jlmonte...@tomitribe.com>> > Gesendet: Mittwoch, 11. Mai 2022 15:57:54 > An: dev@tomee.apache.org<mailto:dev@tomee.apache.org> > Betreff: Re: TomEE 9.x - from javax to jakarta namespace > > Alright, with the latest changes pushed yesterday and today, we are now > at > the exact same numbers for TomEE 8.x / Jakarta EE 8 under JDK8 and TomEE > 9.x / Jakarta 9.1 under JDK17. > > If everyone is ok with it, we can create a new milestone and give users > the > opportunity to provide us with some feedback and to report bugs. > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Tue, May 10, 2022 at 7:06 PM David Blevins > wrote: > > Was checking out the TCK numbers this morning can make to suggest a > 9.0.0-M8 while things look good and found this amazing email. > > The 9.0.x branch is looking absolutely amazing!!! > > What do we think about pushing out a 9.0.0-M8 while things are in their > peak-stable state? I'm sure we'll have to rip up a few more things to > finish off the remaining Jakarta EE and MP TCK issues. Would be great > to > have something that isn't M7 to fallback on as a reference point to > track > regressions. > > Thoughts? > > > -David > > > > On May 10, 2022, at 3:56 AM, Jean-Louis Monteiro < > jlmonte...@tomitribe.com<mailto:jlmonte...@tomitribe.com>> wrote: > > Hi all, > > Time for some reporting > > On our journey to migrate TomEE over from javax to jakarta namespace, > we > had many issues. > After updating all our code, we had to do a bunch of dependency > upgrades > after upgrading many of them (OpenWebbeans, BVal, Geronimo, etc). > > We then faced many issues with non compatible libraries for example > (ActiveMQ, commons-dbcp, CXF, sxc, taglib, etc). So we ended up > repacking > them in our own groupId after using the Maven Shade plugin to > relocate > the > packages. > > We worked on BVal TCK and CDI TCK and we are close to passing them. > > But we had before to solve all our outdated MicroProfile 1.3 stack to > the > most recent and jakarta compatible version. Geronimo implementations > being > far being, we decided to use some SmallRye implementations until we > can > dedicate some time to update our Apache implementations (config, > metrics, > health, openapi, opentracing, fault tolerance). > > Our build is now more stable, but still not green. Some issues are > basically easy to fix and most people could do it (examples for > instance). > > https://ci-builds.apache.org/job/Tomee/job/master-build-full/ > > The integration for openapi, opentracing and fault tolerance is not > done > and we are far from passing the TCK. On config, metrics and health we > are > close. Same for our JWT implementation. > > I also wanted to have a view on the platform TCK, so I decided to > stop > TomEE work in order to spend time on the Platform TCK to do all > dependency > upgrades and get the TCK to run properly. I'm pleased to announce > that > after 2 weeks of hard work, we are 99% compatible > > https://tck.work/tomee/build?id=1652104572445 > > Thanks everyone for t
Re: TomEE 9.x - from javax to jakarta namespace
+1 Best Martin — https://twitter.com/mawiesne Am 11.05.2022 um 19:00 schrieb Cesar Hernandez mailto:cesargu...@gmail.com>>: +1, Thank you! El mié, 11 may 2022 a las 9:06, Daniel Dias Dos Santos (< daniel.dias.analist...@gmail.com<mailto:daniel.dias.analist...@gmail.com>>) escribió: +1 On Wed, May 11, 2022, 12:00 Zowalla, Richard < richard.zowa...@hs-heilbronn.de<mailto:richard.zowa...@hs-heilbronn.de>> wrote: I am fine with it: +1 Von: Jean-Louis Monteiro mailto:jlmonte...@tomitribe.com>> Gesendet: Mittwoch, 11. Mai 2022 15:57:54 An: dev@tomee.apache.org<mailto:dev@tomee.apache.org> Betreff: Re: TomEE 9.x - from javax to jakarta namespace Alright, with the latest changes pushed yesterday and today, we are now at the exact same numbers for TomEE 8.x / Jakarta EE 8 under JDK8 and TomEE 9.x / Jakarta 9.1 under JDK17. If everyone is ok with it, we can create a new milestone and give users the opportunity to provide us with some feedback and to report bugs. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, May 10, 2022 at 7:06 PM David Blevins wrote: Was checking out the TCK numbers this morning can make to suggest a 9.0.0-M8 while things look good and found this amazing email. The 9.0.x branch is looking absolutely amazing!!! What do we think about pushing out a 9.0.0-M8 while things are in their peak-stable state? I'm sure we'll have to rip up a few more things to finish off the remaining Jakarta EE and MP TCK issues. Would be great to have something that isn't M7 to fallback on as a reference point to track regressions. Thoughts? -David On May 10, 2022, at 3:56 AM, Jean-Louis Monteiro < jlmonte...@tomitribe.com<mailto:jlmonte...@tomitribe.com>> wrote: Hi all, Time for some reporting On our journey to migrate TomEE over from javax to jakarta namespace, we had many issues. After updating all our code, we had to do a bunch of dependency upgrades after upgrading many of them (OpenWebbeans, BVal, Geronimo, etc). We then faced many issues with non compatible libraries for example (ActiveMQ, commons-dbcp, CXF, sxc, taglib, etc). So we ended up repacking them in our own groupId after using the Maven Shade plugin to relocate the packages. We worked on BVal TCK and CDI TCK and we are close to passing them. But we had before to solve all our outdated MicroProfile 1.3 stack to the most recent and jakarta compatible version. Geronimo implementations being far being, we decided to use some SmallRye implementations until we can dedicate some time to update our Apache implementations (config, metrics, health, openapi, opentracing, fault tolerance). Our build is now more stable, but still not green. Some issues are basically easy to fix and most people could do it (examples for instance). https://ci-builds.apache.org/job/Tomee/job/master-build-full/ The integration for openapi, opentracing and fault tolerance is not done and we are far from passing the TCK. On config, metrics and health we are close. Same for our JWT implementation. I also wanted to have a view on the platform TCK, so I decided to stop TomEE work in order to spend time on the Platform TCK to do all dependency upgrades and get the TCK to run properly. I'm pleased to announce that after 2 weeks of hard work, we are 99% compatible https://tck.work/tomee/build?id=1652104572445 Thanks everyone for the help. Keep going and if you need some guidance or help, let us know. For coordination purposes, here is the issue https://issues.apache.org/jira/browse/TOMEE-3862 Many subtasks are there and you can create new tasks when needed and ask any committer to assign it to you. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Thu, May 5, 2022 at 11:13 AM Zowalla, Richard < richard.zowa...@hs-heilbronn.de> wrote: Yes - we already yanked it in 9.x Gruß Richard Am Donnerstag, dem 05.05.2022 um 10:10 +0100 schrieb Jonathan Gallimore: Sounds good. I'll drop the transformer from the 8.x branch (looks like we don't use it in 9.x), and I'll create a single example to demonstrate it in a sandbox. Jon On Wed, May 4, 2022 at 12:32 PM Zowalla, Richard < richard.zowa...@hs-heilbronn.de<mailto:richard.zowa...@hs-heilbronn.de>> wrote: You are right - we can remove it imho from 8.x as we do not test with it and the transformed samples might not even work, e.g. dependencies are not migrated, etc. +1 for providing a (bigger) example. Gruß Richard Am Mittwoch, dem 04.05.2022 um 11:17 +0100 schrieb Jonathan Gallimore: I've picked up a task related to the examples: https://issues.apache.org/jira/browse/TOMEE-3873. I specifically went for this, as I added the Eclipse Transformer to the build for a number of examples in the past, back when we were doing the transformation process on TomEE itself. The drawbacks here is that any tests in the examples run on the
Re: TomEE 9.x - from javax to jakarta namespace
+1, Thank you! El mié, 11 may 2022 a las 9:06, Daniel Dias Dos Santos (< daniel.dias.analist...@gmail.com>) escribió: > +1 > > On Wed, May 11, 2022, 12:00 Zowalla, Richard < > richard.zowa...@hs-heilbronn.de> wrote: > > > I am fine with it: +1 > > > > Von: Jean-Louis Monteiro > > Gesendet: Mittwoch, 11. Mai 2022 15:57:54 > > An: dev@tomee.apache.org > > Betreff: Re: TomEE 9.x - from javax to jakarta namespace > > > > Alright, with the latest changes pushed yesterday and today, we are now > at > > the exact same numbers for TomEE 8.x / Jakarta EE 8 under JDK8 and TomEE > > 9.x / Jakarta 9.1 under JDK17. > > > > If everyone is ok with it, we can create a new milestone and give users > the > > opportunity to provide us with some feedback and to report bugs. > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Tue, May 10, 2022 at 7:06 PM David Blevins > > wrote: > > > > > Was checking out the TCK numbers this morning can make to suggest a > > > 9.0.0-M8 while things look good and found this amazing email. > > > > > > The 9.0.x branch is looking absolutely amazing!!! > > > > > > What do we think about pushing out a 9.0.0-M8 while things are in their > > > peak-stable state? I'm sure we'll have to rip up a few more things to > > > finish off the remaining Jakarta EE and MP TCK issues. Would be great > to > > > have something that isn't M7 to fallback on as a reference point to > track > > > regressions. > > > > > > Thoughts? > > > > > > > > > -David > > > > > > > > > > > > > On May 10, 2022, at 3:56 AM, Jean-Louis Monteiro < > > > jlmonte...@tomitribe.com> wrote: > > > > > > > > Hi all, > > > > > > > > Time for some reporting > > > > > > > > On our journey to migrate TomEE over from javax to jakarta namespace, > > we > > > > had many issues. > > > > After updating all our code, we had to do a bunch of dependency > > upgrades > > > > after upgrading many of them (OpenWebbeans, BVal, Geronimo, etc). > > > > > > > > We then faced many issues with non compatible libraries for example > > > > (ActiveMQ, commons-dbcp, CXF, sxc, taglib, etc). So we ended up > > repacking > > > > them in our own groupId after using the Maven Shade plugin to > relocate > > > the > > > > packages. > > > > > > > > We worked on BVal TCK and CDI TCK and we are close to passing them. > > > > > > > > But we had before to solve all our outdated MicroProfile 1.3 stack to > > the > > > > most recent and jakarta compatible version. Geronimo implementations > > > being > > > > far being, we decided to use some SmallRye implementations until we > can > > > > dedicate some time to update our Apache implementations (config, > > metrics, > > > > health, openapi, opentracing, fault tolerance). > > > > > > > > Our build is now more stable, but still not green. Some issues are > > > > basically easy to fix and most people could do it (examples for > > > instance). > > > > > > > > https://ci-builds.apache.org/job/Tomee/job/master-build-full/ > > > > > > > > The integration for openapi, opentracing and fault tolerance is not > > done > > > > and we are far from passing the TCK. On config, metrics and health we > > are > > > > close. Same for our JWT implementation. > > > > > > > > I also wanted to have a view on the platform TCK, so I decided to > stop > > > > TomEE work in order to spend time on the Platform TCK to do all > > > dependency > > > > upgrades and get the TCK to run properly. I'm pleased to announce > that > > > > after 2 weeks of hard work, we are 99% compatible > > > > > > > > https://tck.work/tomee/build?id=1652104572445 > > > > > > > > Thanks everyone for the help. > > > > Keep going and if you need some guidance or help, let us know. > > > > > > > > For coordination purposes, here is the issue > > > > https://issues.apache.org/jira/browse/TOMEE-3862 > > > > Many subtasks are there and you can create new tasks when needed and > > ask > > >
Re: TomEE 9.x - from javax to jakarta namespace
+1 On Wed, May 11, 2022, 12:00 Zowalla, Richard < richard.zowa...@hs-heilbronn.de> wrote: > I am fine with it: +1 > > Von: Jean-Louis Monteiro > Gesendet: Mittwoch, 11. Mai 2022 15:57:54 > An: dev@tomee.apache.org > Betreff: Re: TomEE 9.x - from javax to jakarta namespace > > Alright, with the latest changes pushed yesterday and today, we are now at > the exact same numbers for TomEE 8.x / Jakarta EE 8 under JDK8 and TomEE > 9.x / Jakarta 9.1 under JDK17. > > If everyone is ok with it, we can create a new milestone and give users the > opportunity to provide us with some feedback and to report bugs. > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Tue, May 10, 2022 at 7:06 PM David Blevins > wrote: > > > Was checking out the TCK numbers this morning can make to suggest a > > 9.0.0-M8 while things look good and found this amazing email. > > > > The 9.0.x branch is looking absolutely amazing!!! > > > > What do we think about pushing out a 9.0.0-M8 while things are in their > > peak-stable state? I'm sure we'll have to rip up a few more things to > > finish off the remaining Jakarta EE and MP TCK issues. Would be great to > > have something that isn't M7 to fallback on as a reference point to track > > regressions. > > > > Thoughts? > > > > > > -David > > > > > > > > > On May 10, 2022, at 3:56 AM, Jean-Louis Monteiro < > > jlmonte...@tomitribe.com> wrote: > > > > > > Hi all, > > > > > > Time for some reporting > > > > > > On our journey to migrate TomEE over from javax to jakarta namespace, > we > > > had many issues. > > > After updating all our code, we had to do a bunch of dependency > upgrades > > > after upgrading many of them (OpenWebbeans, BVal, Geronimo, etc). > > > > > > We then faced many issues with non compatible libraries for example > > > (ActiveMQ, commons-dbcp, CXF, sxc, taglib, etc). So we ended up > repacking > > > them in our own groupId after using the Maven Shade plugin to relocate > > the > > > packages. > > > > > > We worked on BVal TCK and CDI TCK and we are close to passing them. > > > > > > But we had before to solve all our outdated MicroProfile 1.3 stack to > the > > > most recent and jakarta compatible version. Geronimo implementations > > being > > > far being, we decided to use some SmallRye implementations until we can > > > dedicate some time to update our Apache implementations (config, > metrics, > > > health, openapi, opentracing, fault tolerance). > > > > > > Our build is now more stable, but still not green. Some issues are > > > basically easy to fix and most people could do it (examples for > > instance). > > > > > > https://ci-builds.apache.org/job/Tomee/job/master-build-full/ > > > > > > The integration for openapi, opentracing and fault tolerance is not > done > > > and we are far from passing the TCK. On config, metrics and health we > are > > > close. Same for our JWT implementation. > > > > > > I also wanted to have a view on the platform TCK, so I decided to stop > > > TomEE work in order to spend time on the Platform TCK to do all > > dependency > > > upgrades and get the TCK to run properly. I'm pleased to announce that > > > after 2 weeks of hard work, we are 99% compatible > > > > > > https://tck.work/tomee/build?id=1652104572445 > > > > > > Thanks everyone for the help. > > > Keep going and if you need some guidance or help, let us know. > > > > > > For coordination purposes, here is the issue > > > https://issues.apache.org/jira/browse/TOMEE-3862 > > > Many subtasks are there and you can create new tasks when needed and > ask > > > any committer to assign it to you. > > > > > > > > > > > > -- > > > Jean-Louis Monteiro > > > http://twitter.com/jlouismonteiro > > > http://www.tomitribe.com > > > > > > > > > On Thu, May 5, 2022 at 11:13 AM Zowalla, Richard < > > > richard.zowa...@hs-heilbronn.de> wrote: > > > > > >> Yes - we already yanked it in 9.x > > >> > > >> Gruß > > >> Richard > > >> > > >> Am Donnerstag, dem 05.05.2022 um 10:10 +0100 schrieb Jonathan > > >> Gallimore: > > >>> Soun
AW: TomEE 9.x - from javax to jakarta namespace
I am fine with it: +1 Von: Jean-Louis Monteiro Gesendet: Mittwoch, 11. Mai 2022 15:57:54 An: dev@tomee.apache.org Betreff: Re: TomEE 9.x - from javax to jakarta namespace Alright, with the latest changes pushed yesterday and today, we are now at the exact same numbers for TomEE 8.x / Jakarta EE 8 under JDK8 and TomEE 9.x / Jakarta 9.1 under JDK17. If everyone is ok with it, we can create a new milestone and give users the opportunity to provide us with some feedback and to report bugs. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, May 10, 2022 at 7:06 PM David Blevins wrote: > Was checking out the TCK numbers this morning can make to suggest a > 9.0.0-M8 while things look good and found this amazing email. > > The 9.0.x branch is looking absolutely amazing!!! > > What do we think about pushing out a 9.0.0-M8 while things are in their > peak-stable state? I'm sure we'll have to rip up a few more things to > finish off the remaining Jakarta EE and MP TCK issues. Would be great to > have something that isn't M7 to fallback on as a reference point to track > regressions. > > Thoughts? > > > -David > > > > > On May 10, 2022, at 3:56 AM, Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > > > > Hi all, > > > > Time for some reporting > > > > On our journey to migrate TomEE over from javax to jakarta namespace, we > > had many issues. > > After updating all our code, we had to do a bunch of dependency upgrades > > after upgrading many of them (OpenWebbeans, BVal, Geronimo, etc). > > > > We then faced many issues with non compatible libraries for example > > (ActiveMQ, commons-dbcp, CXF, sxc, taglib, etc). So we ended up repacking > > them in our own groupId after using the Maven Shade plugin to relocate > the > > packages. > > > > We worked on BVal TCK and CDI TCK and we are close to passing them. > > > > But we had before to solve all our outdated MicroProfile 1.3 stack to the > > most recent and jakarta compatible version. Geronimo implementations > being > > far being, we decided to use some SmallRye implementations until we can > > dedicate some time to update our Apache implementations (config, metrics, > > health, openapi, opentracing, fault tolerance). > > > > Our build is now more stable, but still not green. Some issues are > > basically easy to fix and most people could do it (examples for > instance). > > > > https://ci-builds.apache.org/job/Tomee/job/master-build-full/ > > > > The integration for openapi, opentracing and fault tolerance is not done > > and we are far from passing the TCK. On config, metrics and health we are > > close. Same for our JWT implementation. > > > > I also wanted to have a view on the platform TCK, so I decided to stop > > TomEE work in order to spend time on the Platform TCK to do all > dependency > > upgrades and get the TCK to run properly. I'm pleased to announce that > > after 2 weeks of hard work, we are 99% compatible > > > > https://tck.work/tomee/build?id=1652104572445 > > > > Thanks everyone for the help. > > Keep going and if you need some guidance or help, let us know. > > > > For coordination purposes, here is the issue > > https://issues.apache.org/jira/browse/TOMEE-3862 > > Many subtasks are there and you can create new tasks when needed and ask > > any committer to assign it to you. > > > > > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Thu, May 5, 2022 at 11:13 AM Zowalla, Richard < > > richard.zowa...@hs-heilbronn.de> wrote: > > > >> Yes - we already yanked it in 9.x > >> > >> Gruß > >> Richard > >> > >> Am Donnerstag, dem 05.05.2022 um 10:10 +0100 schrieb Jonathan > >> Gallimore: > >>> Sounds good. I'll drop the transformer from the 8.x branch (looks > >>> like we > >>> don't use it in 9.x), and I'll create a single example to demonstrate > >>> it in > >>> a sandbox. > >>> > >>> Jon > >>> > >>> On Wed, May 4, 2022 at 12:32 PM Zowalla, Richard < > >>> richard.zowa...@hs-heilbronn.de> wrote: > >>> > >>>> You are right - we can remove it imho from 8.x as we do not test > >>>> with > >>>> it and the transformed samples might not even work, e.g. > >>>> dependencies > >>>> are not migrated,
Re: TomEE 9.x - from javax to jakarta namespace
Alright, with the latest changes pushed yesterday and today, we are now at the exact same numbers for TomEE 8.x / Jakarta EE 8 under JDK8 and TomEE 9.x / Jakarta 9.1 under JDK17. If everyone is ok with it, we can create a new milestone and give users the opportunity to provide us with some feedback and to report bugs. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, May 10, 2022 at 7:06 PM David Blevins wrote: > Was checking out the TCK numbers this morning can make to suggest a > 9.0.0-M8 while things look good and found this amazing email. > > The 9.0.x branch is looking absolutely amazing!!! > > What do we think about pushing out a 9.0.0-M8 while things are in their > peak-stable state? I'm sure we'll have to rip up a few more things to > finish off the remaining Jakarta EE and MP TCK issues. Would be great to > have something that isn't M7 to fallback on as a reference point to track > regressions. > > Thoughts? > > > -David > > > > > On May 10, 2022, at 3:56 AM, Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > > > > Hi all, > > > > Time for some reporting > > > > On our journey to migrate TomEE over from javax to jakarta namespace, we > > had many issues. > > After updating all our code, we had to do a bunch of dependency upgrades > > after upgrading many of them (OpenWebbeans, BVal, Geronimo, etc). > > > > We then faced many issues with non compatible libraries for example > > (ActiveMQ, commons-dbcp, CXF, sxc, taglib, etc). So we ended up repacking > > them in our own groupId after using the Maven Shade plugin to relocate > the > > packages. > > > > We worked on BVal TCK and CDI TCK and we are close to passing them. > > > > But we had before to solve all our outdated MicroProfile 1.3 stack to the > > most recent and jakarta compatible version. Geronimo implementations > being > > far being, we decided to use some SmallRye implementations until we can > > dedicate some time to update our Apache implementations (config, metrics, > > health, openapi, opentracing, fault tolerance). > > > > Our build is now more stable, but still not green. Some issues are > > basically easy to fix and most people could do it (examples for > instance). > > > > https://ci-builds.apache.org/job/Tomee/job/master-build-full/ > > > > The integration for openapi, opentracing and fault tolerance is not done > > and we are far from passing the TCK. On config, metrics and health we are > > close. Same for our JWT implementation. > > > > I also wanted to have a view on the platform TCK, so I decided to stop > > TomEE work in order to spend time on the Platform TCK to do all > dependency > > upgrades and get the TCK to run properly. I'm pleased to announce that > > after 2 weeks of hard work, we are 99% compatible > > > > https://tck.work/tomee/build?id=1652104572445 > > > > Thanks everyone for the help. > > Keep going and if you need some guidance or help, let us know. > > > > For coordination purposes, here is the issue > > https://issues.apache.org/jira/browse/TOMEE-3862 > > Many subtasks are there and you can create new tasks when needed and ask > > any committer to assign it to you. > > > > > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Thu, May 5, 2022 at 11:13 AM Zowalla, Richard < > > richard.zowa...@hs-heilbronn.de> wrote: > > > >> Yes - we already yanked it in 9.x > >> > >> Gruß > >> Richard > >> > >> Am Donnerstag, dem 05.05.2022 um 10:10 +0100 schrieb Jonathan > >> Gallimore: > >>> Sounds good. I'll drop the transformer from the 8.x branch (looks > >>> like we > >>> don't use it in 9.x), and I'll create a single example to demonstrate > >>> it in > >>> a sandbox. > >>> > >>> Jon > >>> > >>> On Wed, May 4, 2022 at 12:32 PM Zowalla, Richard < > >>> richard.zowa...@hs-heilbronn.de> wrote: > >>> > You are right - we can remove it imho from 8.x as we do not test > with > it and the transformed samples might not even work, e.g. > dependencies > are not migrated, etc. > > +1 for providing a (bigger) example. > > Gruß > Richard > > Am Mittwoch, dem 04.05.2022 um 11:17 +0100 schrieb Jonathan > Gallimore: > > I've picked up a task related to the examples: > > https://issues.apache.org/jira/browse/TOMEE-3873. I specifically > > went > > for > > this, as I added the Eclipse Transformer to the build for a > > number of > > examples in the past, back when we were doing the transformation > > process on > > TomEE itself. The drawbacks here is that any tests in the > > examples > > run on > > the javax code, and we just "assume" that the transformed > > artifact > > works. I > > would suggest removing that for the master build, as it just > > takes > > build > > time, and the examples should be transformed from javax to > > jakarta at > > source (if they aren't
Re: TomEE 9.x - from javax to jakarta namespace
Was checking out the TCK numbers this morning can make to suggest a 9.0.0-M8 while things look good and found this amazing email. The 9.0.x branch is looking absolutely amazing!!! What do we think about pushing out a 9.0.0-M8 while things are in their peak-stable state? I'm sure we'll have to rip up a few more things to finish off the remaining Jakarta EE and MP TCK issues. Would be great to have something that isn't M7 to fallback on as a reference point to track regressions. Thoughts? -David > On May 10, 2022, at 3:56 AM, Jean-Louis Monteiro > wrote: > > Hi all, > > Time for some reporting > > On our journey to migrate TomEE over from javax to jakarta namespace, we > had many issues. > After updating all our code, we had to do a bunch of dependency upgrades > after upgrading many of them (OpenWebbeans, BVal, Geronimo, etc). > > We then faced many issues with non compatible libraries for example > (ActiveMQ, commons-dbcp, CXF, sxc, taglib, etc). So we ended up repacking > them in our own groupId after using the Maven Shade plugin to relocate the > packages. > > We worked on BVal TCK and CDI TCK and we are close to passing them. > > But we had before to solve all our outdated MicroProfile 1.3 stack to the > most recent and jakarta compatible version. Geronimo implementations being > far being, we decided to use some SmallRye implementations until we can > dedicate some time to update our Apache implementations (config, metrics, > health, openapi, opentracing, fault tolerance). > > Our build is now more stable, but still not green. Some issues are > basically easy to fix and most people could do it (examples for instance). > > https://ci-builds.apache.org/job/Tomee/job/master-build-full/ > > The integration for openapi, opentracing and fault tolerance is not done > and we are far from passing the TCK. On config, metrics and health we are > close. Same for our JWT implementation. > > I also wanted to have a view on the platform TCK, so I decided to stop > TomEE work in order to spend time on the Platform TCK to do all dependency > upgrades and get the TCK to run properly. I'm pleased to announce that > after 2 weeks of hard work, we are 99% compatible > > https://tck.work/tomee/build?id=1652104572445 > > Thanks everyone for the help. > Keep going and if you need some guidance or help, let us know. > > For coordination purposes, here is the issue > https://issues.apache.org/jira/browse/TOMEE-3862 > Many subtasks are there and you can create new tasks when needed and ask > any committer to assign it to you. > > > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Thu, May 5, 2022 at 11:13 AM Zowalla, Richard < > richard.zowa...@hs-heilbronn.de> wrote: > >> Yes - we already yanked it in 9.x >> >> Gruß >> Richard >> >> Am Donnerstag, dem 05.05.2022 um 10:10 +0100 schrieb Jonathan >> Gallimore: >>> Sounds good. I'll drop the transformer from the 8.x branch (looks >>> like we >>> don't use it in 9.x), and I'll create a single example to demonstrate >>> it in >>> a sandbox. >>> >>> Jon >>> >>> On Wed, May 4, 2022 at 12:32 PM Zowalla, Richard < >>> richard.zowa...@hs-heilbronn.de> wrote: >>> You are right - we can remove it imho from 8.x as we do not test with it and the transformed samples might not even work, e.g. dependencies are not migrated, etc. +1 for providing a (bigger) example. Gruß Richard Am Mittwoch, dem 04.05.2022 um 11:17 +0100 schrieb Jonathan Gallimore: > I've picked up a task related to the examples: > https://issues.apache.org/jira/browse/TOMEE-3873. I specifically > went > for > this, as I added the Eclipse Transformer to the build for a > number of > examples in the past, back when we were doing the transformation > process on > TomEE itself. The drawbacks here is that any tests in the > examples > run on > the javax code, and we just "assume" that the transformed > artifact > works. I > would suggest removing that for the master build, as it just > takes > build > time, and the examples should be transformed from javax to > jakarta at > source (if they aren't already). On the TomEE 8 build, we could > select a > few examples (no need to do them all) and find a way to run the > tests > on > both javax and jakarta versions of TomEE. > > Additionally, it would likely be useful to add documentation to > this. > If we > also wanted a bigger example application that specifically covers > transformation, I could look at that too. > > What do you think? > > Jon > > > > On Tue, Mar 22, 2022 at 12:58 PM Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > >> Hi, >> >> I've been working for quite a long time on TomEE 9.x, and it's >> been >> more
Re: TomEE 9.x - from javax to jakarta namespace
Thank you Alex. Community work :-) Still a lot energy to spend before we can get a GA, but moving in the right direction -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, May 10, 2022 at 1:01 PM Alex The Rocker wrote: > Hello Jean-Louis, > > Huge, you rock ! > > Alex > > Le jeu. 24 mars 2022 à 10:27, Jean-Louis Monteiro > a écrit : > > > > Hi, > > > > Some additional notes based on current progress. > > > > We have successfully created a maintenance branch for TomEE 8.x with all > > associated builds on Jenkins. > > > > We have been able to stabilize the work for TomEE 9.x on the PR and > > therefore we merged it to master which is now our main development > branch. > > The quick build is green but the full build still has a lot of test > > failures. Same as for TCK the first iterations make it possible to > > significantly drop the number of failures. The remaining failures are > > usually harder to fix. > > > > We can now divide and conquer. An issue has been created > > https://issues.apache.org/jira/browse/TOMEE-3862 > > We are going to add as many small tasks as possible so people can pick > and > > contribute in parallel. > > > > > > Thanks a lot Richard for all the hard work > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Tue, Mar 22, 2022 at 1:59 PM Jean-Louis Monteiro < > > jlmonte...@tomitribe.com> wrote: > > > > > Hi, > > > > > > I've been working for quite a long time on TomEE 9.x, and it's been > more > > > challenging and painful than I was expecting. I thought it would be > good to > > > give you some sort of status. > > > > > > I created a PR for the work. As a reminder, since Java EE moved to > Eclipse > > > to become Jakarta EE, we had a switch from javax.* namespace to > jakarta.* > > > namespace. This is an impacting change, since all applications and > > > applications servers are built on top of it. > > > > > > In TomEE, we decided to do that change in TomEE. We had previously a > > > bytecode change approach like an application could do. It worked and we > > > were able to get certified. But it had a lot of limitations, so we had > to > > > do the migration in the code and fix all compatibility issues. > > > > > > Here is the PR https://github.com/apache/tomee/pull/814 > > > It has 90+ commits and nearly 5000 files touched (added, removed, > > > updated). I understand it's a lot and it makes it almost impossible to > > > review. But I did not see much approaches in this scenario to create > > > smaller PRs. > > > > > > I created a Jenkins build though available at > > > https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/ > > > > > > It makes it possible to track the progress. There have been steps > forward > > > and steps backward. > > > > > > All the code does not sit under TomEE, we use a bunch of third party > > > projects and libraries. I have been able to contribute, publish jakarta > > > compatible versions and get releases for some of them (Jakarta EE APIs > Uber > > > jar, Geronimo Connectors and Transaction Manager, Geronimo Config, > Health, > > > Metrics, OpenTracing, OpenAPI. OpenJPA, BVal, and OpenWebBeans will be > > > released soon. > > > > > > The big parts is CXF, and ActiveMQ. I had to get them done in TomEE and > > > update all group/artifact ids. It's under deps, alongside with SXC, > DBCP, > > > and others. > > > > > > In terms of removal, I tried to remove old stuff like SAAJ Axis 1 > > > integration, JAX RPC, Management J2EE and a couple of other old things. > > > > > > A lot of other libraries got updated to their latest version when > > > available in the new jakarta namespace. > > > > > > I'm starting to get all the build stable and many modules are passing > now, > > > including all CXF webservices, OpenEJB Core, and others. I can get a > build > > > and run TomEE. > > > > > > Goal is to get a green build asap so we can start working on TCK. > > > The "quick" build is now green. Working on the full build. > > > > > > I'll soon be creating a branch for TomEE 8.x maintenance and merge the > PR. > > > I'm hoping we can then have small PRs or at least more people working > in > > > parallel. > > > > > > -- > > > Jean-Louis Monteiro > > > http://twitter.com/jlouismonteiro > > > http://www.tomitribe.com > > > >
Re: TomEE 9.x - from javax to jakarta namespace
Hello Jean-Louis, Huge, you rock ! Alex Le jeu. 24 mars 2022 à 10:27, Jean-Louis Monteiro a écrit : > > Hi, > > Some additional notes based on current progress. > > We have successfully created a maintenance branch for TomEE 8.x with all > associated builds on Jenkins. > > We have been able to stabilize the work for TomEE 9.x on the PR and > therefore we merged it to master which is now our main development branch. > The quick build is green but the full build still has a lot of test > failures. Same as for TCK the first iterations make it possible to > significantly drop the number of failures. The remaining failures are > usually harder to fix. > > We can now divide and conquer. An issue has been created > https://issues.apache.org/jira/browse/TOMEE-3862 > We are going to add as many small tasks as possible so people can pick and > contribute in parallel. > > > Thanks a lot Richard for all the hard work > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Tue, Mar 22, 2022 at 1:59 PM Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > > > Hi, > > > > I've been working for quite a long time on TomEE 9.x, and it's been more > > challenging and painful than I was expecting. I thought it would be good to > > give you some sort of status. > > > > I created a PR for the work. As a reminder, since Java EE moved to Eclipse > > to become Jakarta EE, we had a switch from javax.* namespace to jakarta.* > > namespace. This is an impacting change, since all applications and > > applications servers are built on top of it. > > > > In TomEE, we decided to do that change in TomEE. We had previously a > > bytecode change approach like an application could do. It worked and we > > were able to get certified. But it had a lot of limitations, so we had to > > do the migration in the code and fix all compatibility issues. > > > > Here is the PR https://github.com/apache/tomee/pull/814 > > It has 90+ commits and nearly 5000 files touched (added, removed, > > updated). I understand it's a lot and it makes it almost impossible to > > review. But I did not see much approaches in this scenario to create > > smaller PRs. > > > > I created a Jenkins build though available at > > https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/ > > > > It makes it possible to track the progress. There have been steps forward > > and steps backward. > > > > All the code does not sit under TomEE, we use a bunch of third party > > projects and libraries. I have been able to contribute, publish jakarta > > compatible versions and get releases for some of them (Jakarta EE APIs Uber > > jar, Geronimo Connectors and Transaction Manager, Geronimo Config, Health, > > Metrics, OpenTracing, OpenAPI. OpenJPA, BVal, and OpenWebBeans will be > > released soon. > > > > The big parts is CXF, and ActiveMQ. I had to get them done in TomEE and > > update all group/artifact ids. It's under deps, alongside with SXC, DBCP, > > and others. > > > > In terms of removal, I tried to remove old stuff like SAAJ Axis 1 > > integration, JAX RPC, Management J2EE and a couple of other old things. > > > > A lot of other libraries got updated to their latest version when > > available in the new jakarta namespace. > > > > I'm starting to get all the build stable and many modules are passing now, > > including all CXF webservices, OpenEJB Core, and others. I can get a build > > and run TomEE. > > > > Goal is to get a green build asap so we can start working on TCK. > > The "quick" build is now green. Working on the full build. > > > > I'll soon be creating a branch for TomEE 8.x maintenance and merge the PR. > > I'm hoping we can then have small PRs or at least more people working in > > parallel. > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > >
Re: TomEE 9.x - from javax to jakarta namespace
Hi all, Time for some reporting On our journey to migrate TomEE over from javax to jakarta namespace, we had many issues. After updating all our code, we had to do a bunch of dependency upgrades after upgrading many of them (OpenWebbeans, BVal, Geronimo, etc). We then faced many issues with non compatible libraries for example (ActiveMQ, commons-dbcp, CXF, sxc, taglib, etc). So we ended up repacking them in our own groupId after using the Maven Shade plugin to relocate the packages. We worked on BVal TCK and CDI TCK and we are close to passing them. But we had before to solve all our outdated MicroProfile 1.3 stack to the most recent and jakarta compatible version. Geronimo implementations being far being, we decided to use some SmallRye implementations until we can dedicate some time to update our Apache implementations (config, metrics, health, openapi, opentracing, fault tolerance). Our build is now more stable, but still not green. Some issues are basically easy to fix and most people could do it (examples for instance). https://ci-builds.apache.org/job/Tomee/job/master-build-full/ The integration for openapi, opentracing and fault tolerance is not done and we are far from passing the TCK. On config, metrics and health we are close. Same for our JWT implementation. I also wanted to have a view on the platform TCK, so I decided to stop TomEE work in order to spend time on the Platform TCK to do all dependency upgrades and get the TCK to run properly. I'm pleased to announce that after 2 weeks of hard work, we are 99% compatible https://tck.work/tomee/build?id=1652104572445 Thanks everyone for the help. Keep going and if you need some guidance or help, let us know. For coordination purposes, here is the issue https://issues.apache.org/jira/browse/TOMEE-3862 Many subtasks are there and you can create new tasks when needed and ask any committer to assign it to you. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Thu, May 5, 2022 at 11:13 AM Zowalla, Richard < richard.zowa...@hs-heilbronn.de> wrote: > Yes - we already yanked it in 9.x > > Gruß > Richard > > Am Donnerstag, dem 05.05.2022 um 10:10 +0100 schrieb Jonathan > Gallimore: > > Sounds good. I'll drop the transformer from the 8.x branch (looks > > like we > > don't use it in 9.x), and I'll create a single example to demonstrate > > it in > > a sandbox. > > > > Jon > > > > On Wed, May 4, 2022 at 12:32 PM Zowalla, Richard < > > richard.zowa...@hs-heilbronn.de> wrote: > > > > > You are right - we can remove it imho from 8.x as we do not test > > > with > > > it and the transformed samples might not even work, e.g. > > > dependencies > > > are not migrated, etc. > > > > > > +1 for providing a (bigger) example. > > > > > > Gruß > > > Richard > > > > > > Am Mittwoch, dem 04.05.2022 um 11:17 +0100 schrieb Jonathan > > > Gallimore: > > > > I've picked up a task related to the examples: > > > > https://issues.apache.org/jira/browse/TOMEE-3873. I specifically > > > > went > > > > for > > > > this, as I added the Eclipse Transformer to the build for a > > > > number of > > > > examples in the past, back when we were doing the transformation > > > > process on > > > > TomEE itself. The drawbacks here is that any tests in the > > > > examples > > > > run on > > > > the javax code, and we just "assume" that the transformed > > > > artifact > > > > works. I > > > > would suggest removing that for the master build, as it just > > > > takes > > > > build > > > > time, and the examples should be transformed from javax to > > > > jakarta at > > > > source (if they aren't already). On the TomEE 8 build, we could > > > > select a > > > > few examples (no need to do them all) and find a way to run the > > > > tests > > > > on > > > > both javax and jakarta versions of TomEE. > > > > > > > > Additionally, it would likely be useful to add documentation to > > > > this. > > > > If we > > > > also wanted a bigger example application that specifically covers > > > > transformation, I could look at that too. > > > > > > > > What do you think? > > > > > > > > Jon > > > > > > > > > > > > > > > > On Tue, Mar 22, 2022 at 12:58 PM Jean-Louis Monteiro < > > > > jlmonte...@tomitribe.com> wrote: > > > > > > > > > Hi, > > > > > > > > > > I've been working for quite a long time on TomEE 9.x, and it's > > > > > been > > > > > more > > > > > challenging and painful than I was expecting. I thought it > > > > > would be > > > > > good to > > > > > give you some sort of status. > > > > > > > > > > I created a PR for the work. As a reminder, since Java EE moved > > > > > to > > > > > Eclipse > > > > > to become Jakarta EE, we had a switch from javax.* namespace to > > > > > jakarta.* > > > > > namespace. This is an impacting change, since all applications > > > > > and > > > > > applications servers are built on top of it. > > > > > > > > > > In TomEE, we decided to do that change in TomEE. We had > > > > > previously > > > > > a > > >
Re: TomEE 9.x - from javax to jakarta namespace
Yes - we already yanked it in 9.x Gruß Richard Am Donnerstag, dem 05.05.2022 um 10:10 +0100 schrieb Jonathan Gallimore: > Sounds good. I'll drop the transformer from the 8.x branch (looks > like we > don't use it in 9.x), and I'll create a single example to demonstrate > it in > a sandbox. > > Jon > > On Wed, May 4, 2022 at 12:32 PM Zowalla, Richard < > richard.zowa...@hs-heilbronn.de> wrote: > > > You are right - we can remove it imho from 8.x as we do not test > > with > > it and the transformed samples might not even work, e.g. > > dependencies > > are not migrated, etc. > > > > +1 for providing a (bigger) example. > > > > Gruß > > Richard > > > > Am Mittwoch, dem 04.05.2022 um 11:17 +0100 schrieb Jonathan > > Gallimore: > > > I've picked up a task related to the examples: > > > https://issues.apache.org/jira/browse/TOMEE-3873. I specifically > > > went > > > for > > > this, as I added the Eclipse Transformer to the build for a > > > number of > > > examples in the past, back when we were doing the transformation > > > process on > > > TomEE itself. The drawbacks here is that any tests in the > > > examples > > > run on > > > the javax code, and we just "assume" that the transformed > > > artifact > > > works. I > > > would suggest removing that for the master build, as it just > > > takes > > > build > > > time, and the examples should be transformed from javax to > > > jakarta at > > > source (if they aren't already). On the TomEE 8 build, we could > > > select a > > > few examples (no need to do them all) and find a way to run the > > > tests > > > on > > > both javax and jakarta versions of TomEE. > > > > > > Additionally, it would likely be useful to add documentation to > > > this. > > > If we > > > also wanted a bigger example application that specifically covers > > > transformation, I could look at that too. > > > > > > What do you think? > > > > > > Jon > > > > > > > > > > > > On Tue, Mar 22, 2022 at 12:58 PM Jean-Louis Monteiro < > > > jlmonte...@tomitribe.com> wrote: > > > > > > > Hi, > > > > > > > > I've been working for quite a long time on TomEE 9.x, and it's > > > > been > > > > more > > > > challenging and painful than I was expecting. I thought it > > > > would be > > > > good to > > > > give you some sort of status. > > > > > > > > I created a PR for the work. As a reminder, since Java EE moved > > > > to > > > > Eclipse > > > > to become Jakarta EE, we had a switch from javax.* namespace to > > > > jakarta.* > > > > namespace. This is an impacting change, since all applications > > > > and > > > > applications servers are built on top of it. > > > > > > > > In TomEE, we decided to do that change in TomEE. We had > > > > previously > > > > a > > > > bytecode change approach like an application could do. It > > > > worked > > > > and we > > > > were able to get certified. But it had a lot of limitations, so > > > > we > > > > had to > > > > do the migration in the code and fix all compatibility issues. > > > > > > > > Here is the PR https://github.com/apache/tomee/pull/814 > > > > It has 90+ commits and nearly 5000 files touched (added, > > > > removed, > > > > updated). > > > > I understand it's a lot and it makes it almost impossible to > > > > review. But I > > > > did not see much approaches in this scenario to create smaller > > > > PRs. > > > > > > > > I created a Jenkins build though available at > > > > https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/ > > > > > > > > It makes it possible to track the progress. There have been > > > > steps > > > > forward > > > > and steps backward. > > > > > > > > All the code does not sit under TomEE, we use a bunch of third > > > > party > > > > projects and libraries. I have been able to contribute, publish > > > > jakarta > > > > compatible versions and get releases for some of them (Jakarta > > > > EE > > > > APIs Uber > > > > jar, Geronimo Connectors and Transaction Manager, Geronimo > > > > Config, > > > > Health, > > > > Metrics, OpenTracing, OpenAPI. OpenJPA, BVal, and OpenWebBeans > > > > will > > > > be > > > > released soon. > > > > > > > > The big parts is CXF, and ActiveMQ. I had to get them done in > > > > TomEE > > > > and > > > > update all group/artifact ids. It's under deps, alongside with > > > > SXC, > > > > DBCP, > > > > and others. > > > > > > > > In terms of removal, I tried to remove old stuff like SAAJ Axis > > > > 1 > > > > integration, JAX RPC, Management J2EE and a couple of other old > > > > things. > > > > > > > > A lot of other libraries got updated to their latest version > > > > when > > > > available > > > > in the new jakarta namespace. > > > > > > > > I'm starting to get all the build stable and many modules are > > > > passing now, > > > > including all CXF webservices, OpenEJB Core, and others. I can > > > > get > > > > a build > > > > and run TomEE. > > > > > > > > Goal is to get a green build asap so we can start working on > > > > TCK. > > > > The "quick"
Re: TomEE 9.x - from javax to jakarta namespace
Sounds good. I'll drop the transformer from the 8.x branch (looks like we don't use it in 9.x), and I'll create a single example to demonstrate it in a sandbox. Jon On Wed, May 4, 2022 at 12:32 PM Zowalla, Richard < richard.zowa...@hs-heilbronn.de> wrote: > You are right - we can remove it imho from 8.x as we do not test with > it and the transformed samples might not even work, e.g. dependencies > are not migrated, etc. > > +1 for providing a (bigger) example. > > Gruß > Richard > > Am Mittwoch, dem 04.05.2022 um 11:17 +0100 schrieb Jonathan Gallimore: > > I've picked up a task related to the examples: > > https://issues.apache.org/jira/browse/TOMEE-3873. I specifically went > > for > > this, as I added the Eclipse Transformer to the build for a number of > > examples in the past, back when we were doing the transformation > > process on > > TomEE itself. The drawbacks here is that any tests in the examples > > run on > > the javax code, and we just "assume" that the transformed artifact > > works. I > > would suggest removing that for the master build, as it just takes > > build > > time, and the examples should be transformed from javax to jakarta at > > source (if they aren't already). On the TomEE 8 build, we could > > select a > > few examples (no need to do them all) and find a way to run the tests > > on > > both javax and jakarta versions of TomEE. > > > > Additionally, it would likely be useful to add documentation to this. > > If we > > also wanted a bigger example application that specifically covers > > transformation, I could look at that too. > > > > What do you think? > > > > Jon > > > > > > > > On Tue, Mar 22, 2022 at 12:58 PM Jean-Louis Monteiro < > > jlmonte...@tomitribe.com> wrote: > > > > > Hi, > > > > > > I've been working for quite a long time on TomEE 9.x, and it's been > > > more > > > challenging and painful than I was expecting. I thought it would be > > > good to > > > give you some sort of status. > > > > > > I created a PR for the work. As a reminder, since Java EE moved to > > > Eclipse > > > to become Jakarta EE, we had a switch from javax.* namespace to > > > jakarta.* > > > namespace. This is an impacting change, since all applications and > > > applications servers are built on top of it. > > > > > > In TomEE, we decided to do that change in TomEE. We had previously > > > a > > > bytecode change approach like an application could do. It worked > > > and we > > > were able to get certified. But it had a lot of limitations, so we > > > had to > > > do the migration in the code and fix all compatibility issues. > > > > > > Here is the PR https://github.com/apache/tomee/pull/814 > > > It has 90+ commits and nearly 5000 files touched (added, removed, > > > updated). > > > I understand it's a lot and it makes it almost impossible to > > > review. But I > > > did not see much approaches in this scenario to create smaller PRs. > > > > > > I created a Jenkins build though available at > > > https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/ > > > > > > It makes it possible to track the progress. There have been steps > > > forward > > > and steps backward. > > > > > > All the code does not sit under TomEE, we use a bunch of third > > > party > > > projects and libraries. I have been able to contribute, publish > > > jakarta > > > compatible versions and get releases for some of them (Jakarta EE > > > APIs Uber > > > jar, Geronimo Connectors and Transaction Manager, Geronimo Config, > > > Health, > > > Metrics, OpenTracing, OpenAPI. OpenJPA, BVal, and OpenWebBeans will > > > be > > > released soon. > > > > > > The big parts is CXF, and ActiveMQ. I had to get them done in TomEE > > > and > > > update all group/artifact ids. It's under deps, alongside with SXC, > > > DBCP, > > > and others. > > > > > > In terms of removal, I tried to remove old stuff like SAAJ Axis 1 > > > integration, JAX RPC, Management J2EE and a couple of other old > > > things. > > > > > > A lot of other libraries got updated to their latest version when > > > available > > > in the new jakarta namespace. > > > > > > I'm starting to get all the build stable and many modules are > > > passing now, > > > including all CXF webservices, OpenEJB Core, and others. I can get > > > a build > > > and run TomEE. > > > > > > Goal is to get a green build asap so we can start working on TCK. > > > The "quick" build is now green. Working on the full build. > > > > > > I'll soon be creating a branch for TomEE 8.x maintenance and merge > > > the PR. > > > I'm hoping we can then have small PRs or at least more people > > > working in > > > parallel. > > > > > > -- > > > Jean-Louis Monteiro > > > http://twitter.com/jlouismonteiro > > > http://www.tomitribe.com > > > >
Re: TomEE 9.x - from javax to jakarta namespace
Hello, +1 On Wed, May 4, 2022, 11:27 Cesar Hernandez wrote: > +1 Jonathan. > > > On Wed, May 4, 2022 at 05:32 Zowalla, Richard < > richard.zowa...@hs-heilbronn.de> wrote: > > > You are right - we can remove it imho from 8.x as we do not test with > > it and the transformed samples might not even work, e.g. dependencies > > are not migrated, etc. > > > > +1 for providing a (bigger) example. > > > > Gruß > > Richard > > > > Am Mittwoch, dem 04.05.2022 um 11:17 +0100 schrieb Jonathan Gallimore: > > > I've picked up a task related to the examples: > > > https://issues.apache.org/jira/browse/TOMEE-3873. I specifically went > > > for > > > this, as I added the Eclipse Transformer to the build for a number of > > > examples in the past, back when we were doing the transformation > > > process on > > > TomEE itself. The drawbacks here is that any tests in the examples > > > run on > > > the javax code, and we just "assume" that the transformed artifact > > > works. I > > > would suggest removing that for the master build, as it just takes > > > build > > > time, and the examples should be transformed from javax to jakarta at > > > source (if they aren't already). On the TomEE 8 build, we could > > > select a > > > few examples (no need to do them all) and find a way to run the tests > > > on > > > both javax and jakarta versions of TomEE. > > > > > > Additionally, it would likely be useful to add documentation to this. > > > If we > > > also wanted a bigger example application that specifically covers > > > transformation, I could look at that too. > > > > > > What do you think? > > > > > > Jon > > > > > > > > > > > > On Tue, Mar 22, 2022 at 12:58 PM Jean-Louis Monteiro < > > > jlmonte...@tomitribe.com> wrote: > > > > > > > Hi, > > > > > > > > I've been working for quite a long time on TomEE 9.x, and it's been > > > > more > > > > challenging and painful than I was expecting. I thought it would be > > > > good to > > > > give you some sort of status. > > > > > > > > I created a PR for the work. As a reminder, since Java EE moved to > > > > Eclipse > > > > to become Jakarta EE, we had a switch from javax.* namespace to > > > > jakarta.* > > > > namespace. This is an impacting change, since all applications and > > > > applications servers are built on top of it. > > > > > > > > In TomEE, we decided to do that change in TomEE. We had previously > > > > a > > > > bytecode change approach like an application could do. It worked > > > > and we > > > > were able to get certified. But it had a lot of limitations, so we > > > > had to > > > > do the migration in the code and fix all compatibility issues. > > > > > > > > Here is the PR https://github.com/apache/tomee/pull/814 > > > > It has 90+ commits and nearly 5000 files touched (added, removed, > > > > updated). > > > > I understand it's a lot and it makes it almost impossible to > > > > review. But I > > > > did not see much approaches in this scenario to create smaller PRs. > > > > > > > > I created a Jenkins build though available at > > > > https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/ > > > > > > > > It makes it possible to track the progress. There have been steps > > > > forward > > > > and steps backward. > > > > > > > > All the code does not sit under TomEE, we use a bunch of third > > > > party > > > > projects and libraries. I have been able to contribute, publish > > > > jakarta > > > > compatible versions and get releases for some of them (Jakarta EE > > > > APIs Uber > > > > jar, Geronimo Connectors and Transaction Manager, Geronimo Config, > > > > Health, > > > > Metrics, OpenTracing, OpenAPI. OpenJPA, BVal, and OpenWebBeans will > > > > be > > > > released soon. > > > > > > > > The big parts is CXF, and ActiveMQ. I had to get them done in TomEE > > > > and > > > > update all group/artifact ids. It's under deps, alongside with SXC, > > > > DBCP, > > > > and others. > > > > > > > > In terms of removal, I tried to remove old stuff like SAAJ Axis 1 > > > > integration, JAX RPC, Management J2EE and a couple of other old > > > > things. > > > > > > > > A lot of other libraries got updated to their latest version when > > > > available > > > > in the new jakarta namespace. > > > > > > > > I'm starting to get all the build stable and many modules are > > > > passing now, > > > > including all CXF webservices, OpenEJB Core, and others. I can get > > > > a build > > > > and run TomEE. > > > > > > > > Goal is to get a green build asap so we can start working on TCK. > > > > The "quick" build is now green. Working on the full build. > > > > > > > > I'll soon be creating a branch for TomEE 8.x maintenance and merge > > > > the PR. > > > > I'm hoping we can then have small PRs or at least more people > > > > working in > > > > parallel. > > > > > > > > -- > > > > Jean-Louis Monteiro > > > > http://twitter.com/jlouismonteiro > > > > http://www.tomitribe.com > > > > > > > -- > Atentamente: > César Hernández. >
Re: TomEE 9.x - from javax to jakarta namespace
+1 Jonathan. On Wed, May 4, 2022 at 05:32 Zowalla, Richard < richard.zowa...@hs-heilbronn.de> wrote: > You are right - we can remove it imho from 8.x as we do not test with > it and the transformed samples might not even work, e.g. dependencies > are not migrated, etc. > > +1 for providing a (bigger) example. > > Gruß > Richard > > Am Mittwoch, dem 04.05.2022 um 11:17 +0100 schrieb Jonathan Gallimore: > > I've picked up a task related to the examples: > > https://issues.apache.org/jira/browse/TOMEE-3873. I specifically went > > for > > this, as I added the Eclipse Transformer to the build for a number of > > examples in the past, back when we were doing the transformation > > process on > > TomEE itself. The drawbacks here is that any tests in the examples > > run on > > the javax code, and we just "assume" that the transformed artifact > > works. I > > would suggest removing that for the master build, as it just takes > > build > > time, and the examples should be transformed from javax to jakarta at > > source (if they aren't already). On the TomEE 8 build, we could > > select a > > few examples (no need to do them all) and find a way to run the tests > > on > > both javax and jakarta versions of TomEE. > > > > Additionally, it would likely be useful to add documentation to this. > > If we > > also wanted a bigger example application that specifically covers > > transformation, I could look at that too. > > > > What do you think? > > > > Jon > > > > > > > > On Tue, Mar 22, 2022 at 12:58 PM Jean-Louis Monteiro < > > jlmonte...@tomitribe.com> wrote: > > > > > Hi, > > > > > > I've been working for quite a long time on TomEE 9.x, and it's been > > > more > > > challenging and painful than I was expecting. I thought it would be > > > good to > > > give you some sort of status. > > > > > > I created a PR for the work. As a reminder, since Java EE moved to > > > Eclipse > > > to become Jakarta EE, we had a switch from javax.* namespace to > > > jakarta.* > > > namespace. This is an impacting change, since all applications and > > > applications servers are built on top of it. > > > > > > In TomEE, we decided to do that change in TomEE. We had previously > > > a > > > bytecode change approach like an application could do. It worked > > > and we > > > were able to get certified. But it had a lot of limitations, so we > > > had to > > > do the migration in the code and fix all compatibility issues. > > > > > > Here is the PR https://github.com/apache/tomee/pull/814 > > > It has 90+ commits and nearly 5000 files touched (added, removed, > > > updated). > > > I understand it's a lot and it makes it almost impossible to > > > review. But I > > > did not see much approaches in this scenario to create smaller PRs. > > > > > > I created a Jenkins build though available at > > > https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/ > > > > > > It makes it possible to track the progress. There have been steps > > > forward > > > and steps backward. > > > > > > All the code does not sit under TomEE, we use a bunch of third > > > party > > > projects and libraries. I have been able to contribute, publish > > > jakarta > > > compatible versions and get releases for some of them (Jakarta EE > > > APIs Uber > > > jar, Geronimo Connectors and Transaction Manager, Geronimo Config, > > > Health, > > > Metrics, OpenTracing, OpenAPI. OpenJPA, BVal, and OpenWebBeans will > > > be > > > released soon. > > > > > > The big parts is CXF, and ActiveMQ. I had to get them done in TomEE > > > and > > > update all group/artifact ids. It's under deps, alongside with SXC, > > > DBCP, > > > and others. > > > > > > In terms of removal, I tried to remove old stuff like SAAJ Axis 1 > > > integration, JAX RPC, Management J2EE and a couple of other old > > > things. > > > > > > A lot of other libraries got updated to their latest version when > > > available > > > in the new jakarta namespace. > > > > > > I'm starting to get all the build stable and many modules are > > > passing now, > > > including all CXF webservices, OpenEJB Core, and others. I can get > > > a build > > > and run TomEE. > > > > > > Goal is to get a green build asap so we can start working on TCK. > > > The "quick" build is now green. Working on the full build. > > > > > > I'll soon be creating a branch for TomEE 8.x maintenance and merge > > > the PR. > > > I'm hoping we can then have small PRs or at least more people > > > working in > > > parallel. > > > > > > -- > > > Jean-Louis Monteiro > > > http://twitter.com/jlouismonteiro > > > http://www.tomitribe.com > > > > -- Atentamente: César Hernández.
Re: TomEE 9.x - from javax to jakarta namespace
You are right - we can remove it imho from 8.x as we do not test with it and the transformed samples might not even work, e.g. dependencies are not migrated, etc. +1 for providing a (bigger) example. Gruß Richard Am Mittwoch, dem 04.05.2022 um 11:17 +0100 schrieb Jonathan Gallimore: > I've picked up a task related to the examples: > https://issues.apache.org/jira/browse/TOMEE-3873. I specifically went > for > this, as I added the Eclipse Transformer to the build for a number of > examples in the past, back when we were doing the transformation > process on > TomEE itself. The drawbacks here is that any tests in the examples > run on > the javax code, and we just "assume" that the transformed artifact > works. I > would suggest removing that for the master build, as it just takes > build > time, and the examples should be transformed from javax to jakarta at > source (if they aren't already). On the TomEE 8 build, we could > select a > few examples (no need to do them all) and find a way to run the tests > on > both javax and jakarta versions of TomEE. > > Additionally, it would likely be useful to add documentation to this. > If we > also wanted a bigger example application that specifically covers > transformation, I could look at that too. > > What do you think? > > Jon > > > > On Tue, Mar 22, 2022 at 12:58 PM Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > > > Hi, > > > > I've been working for quite a long time on TomEE 9.x, and it's been > > more > > challenging and painful than I was expecting. I thought it would be > > good to > > give you some sort of status. > > > > I created a PR for the work. As a reminder, since Java EE moved to > > Eclipse > > to become Jakarta EE, we had a switch from javax.* namespace to > > jakarta.* > > namespace. This is an impacting change, since all applications and > > applications servers are built on top of it. > > > > In TomEE, we decided to do that change in TomEE. We had previously > > a > > bytecode change approach like an application could do. It worked > > and we > > were able to get certified. But it had a lot of limitations, so we > > had to > > do the migration in the code and fix all compatibility issues. > > > > Here is the PR https://github.com/apache/tomee/pull/814 > > It has 90+ commits and nearly 5000 files touched (added, removed, > > updated). > > I understand it's a lot and it makes it almost impossible to > > review. But I > > did not see much approaches in this scenario to create smaller PRs. > > > > I created a Jenkins build though available at > > https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/ > > > > It makes it possible to track the progress. There have been steps > > forward > > and steps backward. > > > > All the code does not sit under TomEE, we use a bunch of third > > party > > projects and libraries. I have been able to contribute, publish > > jakarta > > compatible versions and get releases for some of them (Jakarta EE > > APIs Uber > > jar, Geronimo Connectors and Transaction Manager, Geronimo Config, > > Health, > > Metrics, OpenTracing, OpenAPI. OpenJPA, BVal, and OpenWebBeans will > > be > > released soon. > > > > The big parts is CXF, and ActiveMQ. I had to get them done in TomEE > > and > > update all group/artifact ids. It's under deps, alongside with SXC, > > DBCP, > > and others. > > > > In terms of removal, I tried to remove old stuff like SAAJ Axis 1 > > integration, JAX RPC, Management J2EE and a couple of other old > > things. > > > > A lot of other libraries got updated to their latest version when > > available > > in the new jakarta namespace. > > > > I'm starting to get all the build stable and many modules are > > passing now, > > including all CXF webservices, OpenEJB Core, and others. I can get > > a build > > and run TomEE. > > > > Goal is to get a green build asap so we can start working on TCK. > > The "quick" build is now green. Working on the full build. > > > > I'll soon be creating a branch for TomEE 8.x maintenance and merge > > the PR. > > I'm hoping we can then have small PRs or at least more people > > working in > > parallel. > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > smime.p7s Description: S/MIME cryptographic signature
Re: TomEE 9.x - from javax to jakarta namespace
I've picked up a task related to the examples: https://issues.apache.org/jira/browse/TOMEE-3873. I specifically went for this, as I added the Eclipse Transformer to the build for a number of examples in the past, back when we were doing the transformation process on TomEE itself. The drawbacks here is that any tests in the examples run on the javax code, and we just "assume" that the transformed artifact works. I would suggest removing that for the master build, as it just takes build time, and the examples should be transformed from javax to jakarta at source (if they aren't already). On the TomEE 8 build, we could select a few examples (no need to do them all) and find a way to run the tests on both javax and jakarta versions of TomEE. Additionally, it would likely be useful to add documentation to this. If we also wanted a bigger example application that specifically covers transformation, I could look at that too. What do you think? Jon On Tue, Mar 22, 2022 at 12:58 PM Jean-Louis Monteiro < jlmonte...@tomitribe.com> wrote: > Hi, > > I've been working for quite a long time on TomEE 9.x, and it's been more > challenging and painful than I was expecting. I thought it would be good to > give you some sort of status. > > I created a PR for the work. As a reminder, since Java EE moved to Eclipse > to become Jakarta EE, we had a switch from javax.* namespace to jakarta.* > namespace. This is an impacting change, since all applications and > applications servers are built on top of it. > > In TomEE, we decided to do that change in TomEE. We had previously a > bytecode change approach like an application could do. It worked and we > were able to get certified. But it had a lot of limitations, so we had to > do the migration in the code and fix all compatibility issues. > > Here is the PR https://github.com/apache/tomee/pull/814 > It has 90+ commits and nearly 5000 files touched (added, removed, updated). > I understand it's a lot and it makes it almost impossible to review. But I > did not see much approaches in this scenario to create smaller PRs. > > I created a Jenkins build though available at > https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/ > > It makes it possible to track the progress. There have been steps forward > and steps backward. > > All the code does not sit under TomEE, we use a bunch of third party > projects and libraries. I have been able to contribute, publish jakarta > compatible versions and get releases for some of them (Jakarta EE APIs Uber > jar, Geronimo Connectors and Transaction Manager, Geronimo Config, Health, > Metrics, OpenTracing, OpenAPI. OpenJPA, BVal, and OpenWebBeans will be > released soon. > > The big parts is CXF, and ActiveMQ. I had to get them done in TomEE and > update all group/artifact ids. It's under deps, alongside with SXC, DBCP, > and others. > > In terms of removal, I tried to remove old stuff like SAAJ Axis 1 > integration, JAX RPC, Management J2EE and a couple of other old things. > > A lot of other libraries got updated to their latest version when available > in the new jakarta namespace. > > I'm starting to get all the build stable and many modules are passing now, > including all CXF webservices, OpenEJB Core, and others. I can get a build > and run TomEE. > > Goal is to get a green build asap so we can start working on TCK. > The "quick" build is now green. Working on the full build. > > I'll soon be creating a branch for TomEE 8.x maintenance and merge the PR. > I'm hoping we can then have small PRs or at least more people working in > parallel. > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com >
Re: TomEE 9.x - from javax to jakarta namespace
Thank you, I push the fixes. El mar, 3 may 2022 a las 10:50, Zowalla, Richard (< richard.zowa...@hs-heilbronn.de>) escribió: > Thanks, Cesar. I left some comments. > > Am Montag, dem 02.05.2022 um 21:01 -0600 schrieb Cesar Hernandez: > > I created https://issues.apache.org/jira/browse/TOMEE-3932 and the PR > > with > > the first iteration of the document is ready for review. > > https://github.com/apache/tomee/pull/878 > > > > El sáb, 30 abr 2022 a las 0:26, Zowalla, Richard (< > > richard.zowa...@hs-heilbronn.de>) escribió: > > > > > Sounds good: +1 > > > > > > Am Freitag, dem 29.04.2022 um 11:06 +0200 schrieb Jean-Louis > > > Monteiro: > > > > That sounds great Cesar. Thanks > > > > -- > > > > Jean-Louis Monteiro > > > > http://twitter.com/jlouismonteiro > > > > http://www.tomitribe.com > > > > > > > > > > > > On Fri, Apr 29, 2022 at 5:48 AM Cesar Hernandez < > > > > cesargu...@gmail.com > > > > wrote: > > > > > > > > > Thank you for the list, Richard, > > > > > > > > > > If there is no objection, I propose to create a > > > > > https://github.com/apache/tomee/javaxToJakartaNamespace.adoc t > > > > > o > > > > > keep > > > > > track > > > > > of the shaded versions we currently have, common dependencies > > > > > that > > > > > will > > > > > need to be updated, and strategies to troubleshooting common > > > > > issues > > > > > and > > > > > link to the main epic > > > > > https://issues.apache.org/jira/browse/TOMEE-3862. > > > > > > > > > > WDYT? > > > > > > > > > > > > > > > > > > > > El mié, 27 abr 2022 a las 0:23, Zowalla, Richard (< > > > > > richard.zowa...@hs-heilbronn.de>) escribió: > > > > > > > > > > > Hi, > > > > > > > > > > > > I am not aware of any public reference list. There are some > > > > > > things, > > > > > > which floated around the mailing list or in the heads, which > > > > > > are: > > > > > > > > > > > > - Javamail is currently broken. We need to have a jakarta > > > > > > compatible > > > > > > version of Geronimo Javamail. This currently breaks 2 > > > > > > examples > > > > > > and > > > > > > prevents platform tck from running. > > > > > > > > > > > > - Deltaspike / Kratzo examples require dependency upgrades, > > > > > > i.e. > > > > > > MVC > > > > > > 2.0 + Jakarta version of Deltaspike. > > > > > > > > > > > > - Micro Profile examples are broken due to the ongoing > > > > > > integration work > > > > > > of SmallRye impls. If the integration is done, we can fix > > > > > > them. > > > > > > > > > > > > - If Hibernate is used, we either need to upgrade to 6.0.0 > > > > > > _or_ > > > > > > use the > > > > > > Jakarta artifact from the 5.6.x series. In some examples, we > > > > > > still use > > > > > > Hibernate 4, so the upgrade also requires to deal with > > > > > > "tomee.jpa.factory.lazy". > > > > > > > > > > > > - Check for "http" repositories to avoid the default http > > > > > > blocker > > > > > > in > > > > > > newer Maven versions. > > > > > > > > > > > > Gruß > > > > > > Richard > > > > > > > > > > > > > > > > > > Am Dienstag, dem 26.04.2022 um 21:28 -0600 schrieb Cesar > > > > > > Hernandez: > > > > > > > Hi all, > > > > > > > > > > > > > > Late last week I started to pick and create sub-task > > > > > > > related to > > > > > > > https://issues.apache.org/jira/browse/TOMEE-3862. > > > > > > > The current CI master status [1] has helped me to identify > > > > > > > tests that > > > > > > > need > > > > > > > fixes, examples that need dependencies updates to match the > > > > > > > javax. -> > > > > > > > jakarta , etc. > > > > > > > > > > > > > > Do we have a place where we can check the list of knowing- > > > > > > > Issue > > > > > > > and > > > > > > > knowing-fixes a contributor can take as a reference when > > > > > > > trying > > > > > > > to > > > > > > > fix a > > > > > > > subtask from TOMEE-3862 ? > > > > > > > For example, today I faced a javax/servlet issue [2] that > > > > > > > required > > > > > > > some > > > > > > > dependencies replacements like jstl [3 ] with > > > > > > > jakarta.servlet.jsp.jstl-api > > > > > > > [4] and taglibs:standard [5] with taglibs-shade [6]. > > > > > > > > > > > > > > > > > > > > > [1] > > > > > > > https://ci-builds.apache.org/job/Tomee/job/master-build-full/ > > > > > > > > > > > > > > [2] > > > > > > > > > > > > > > Caused by: java.lang.NoClassDefFoundError: > > > > > > > javax/servlet/jsp/tagext/TagSupport > > > > > > > > > > > > > > > > > > > > > [3] > > > > > > > javax.servlet > > > > > > > jstl > > > > > > > 1.1.2 > > > > > > > > > > > > > > [4] > > > > > > > jakarta.servlet.jsp.jstl > > > > > > > jakarta.servlet.jsp.jstl-api > > > > > > > 2.0.0 > > > > > > > > > > > > > > [5] > > > > > > > taglibs > > > > > > > standard > > > > > > > 1.1.2 > > > > > > > > > > > > > > [6] > > > > > > > org.apache.tomee > > > > > > > taglibs-shade > > > > > > > 9.0.0-M8-SNAPSHOT > > > > > > > > > > > > > > > > > > > > > El mié, 30 mar 2022 a las 1:20, Jean-Louis Monteiro (< > > > > > > > jlmonte...@tomitribe.com>)
Re: TomEE 9.x - from javax to jakarta namespace
Thanks, Cesar. I left some comments. Am Montag, dem 02.05.2022 um 21:01 -0600 schrieb Cesar Hernandez: > I created https://issues.apache.org/jira/browse/TOMEE-3932 and the PR > with > the first iteration of the document is ready for review. > https://github.com/apache/tomee/pull/878 > > El sáb, 30 abr 2022 a las 0:26, Zowalla, Richard (< > richard.zowa...@hs-heilbronn.de>) escribió: > > > Sounds good: +1 > > > > Am Freitag, dem 29.04.2022 um 11:06 +0200 schrieb Jean-Louis > > Monteiro: > > > That sounds great Cesar. Thanks > > > -- > > > Jean-Louis Monteiro > > > http://twitter.com/jlouismonteiro > > > http://www.tomitribe.com > > > > > > > > > On Fri, Apr 29, 2022 at 5:48 AM Cesar Hernandez < > > > cesargu...@gmail.com > > > wrote: > > > > > > > Thank you for the list, Richard, > > > > > > > > If there is no objection, I propose to create a > > > > https://github.com/apache/tomee/javaxToJakartaNamespace.adoc t > > > > o > > > > keep > > > > track > > > > of the shaded versions we currently have, common dependencies > > > > that > > > > will > > > > need to be updated, and strategies to troubleshooting common > > > > issues > > > > and > > > > link to the main epic > > > > https://issues.apache.org/jira/browse/TOMEE-3862. > > > > > > > > WDYT? > > > > > > > > > > > > > > > > El mié, 27 abr 2022 a las 0:23, Zowalla, Richard (< > > > > richard.zowa...@hs-heilbronn.de>) escribió: > > > > > > > > > Hi, > > > > > > > > > > I am not aware of any public reference list. There are some > > > > > things, > > > > > which floated around the mailing list or in the heads, which > > > > > are: > > > > > > > > > > - Javamail is currently broken. We need to have a jakarta > > > > > compatible > > > > > version of Geronimo Javamail. This currently breaks 2 > > > > > examples > > > > > and > > > > > prevents platform tck from running. > > > > > > > > > > - Deltaspike / Kratzo examples require dependency upgrades, > > > > > i.e. > > > > > MVC > > > > > 2.0 + Jakarta version of Deltaspike. > > > > > > > > > > - Micro Profile examples are broken due to the ongoing > > > > > integration work > > > > > of SmallRye impls. If the integration is done, we can fix > > > > > them. > > > > > > > > > > - If Hibernate is used, we either need to upgrade to 6.0.0 > > > > > _or_ > > > > > use the > > > > > Jakarta artifact from the 5.6.x series. In some examples, we > > > > > still use > > > > > Hibernate 4, so the upgrade also requires to deal with > > > > > "tomee.jpa.factory.lazy". > > > > > > > > > > - Check for "http" repositories to avoid the default http > > > > > blocker > > > > > in > > > > > newer Maven versions. > > > > > > > > > > Gruß > > > > > Richard > > > > > > > > > > > > > > > Am Dienstag, dem 26.04.2022 um 21:28 -0600 schrieb Cesar > > > > > Hernandez: > > > > > > Hi all, > > > > > > > > > > > > Late last week I started to pick and create sub-task > > > > > > related to > > > > > > https://issues.apache.org/jira/browse/TOMEE-3862. > > > > > > The current CI master status [1] has helped me to identify > > > > > > tests that > > > > > > need > > > > > > fixes, examples that need dependencies updates to match the > > > > > > javax. -> > > > > > > jakarta , etc. > > > > > > > > > > > > Do we have a place where we can check the list of knowing- > > > > > > Issue > > > > > > and > > > > > > knowing-fixes a contributor can take as a reference when > > > > > > trying > > > > > > to > > > > > > fix a > > > > > > subtask from TOMEE-3862 ? > > > > > > For example, today I faced a javax/servlet issue [2] that > > > > > > required > > > > > > some > > > > > > dependencies replacements like jstl [3 ] with > > > > > > jakarta.servlet.jsp.jstl-api > > > > > > [4] and taglibs:standard [5] with taglibs-shade [6]. > > > > > > > > > > > > > > > > > > [1] > > > > > > https://ci-builds.apache.org/job/Tomee/job/master-build-full/ > > > > > > > > > > > > [2] > > > > > > > > > > > > Caused by: java.lang.NoClassDefFoundError: > > > > > > javax/servlet/jsp/tagext/TagSupport > > > > > > > > > > > > > > > > > > [3] > > > > > > javax.servlet > > > > > > jstl > > > > > > 1.1.2 > > > > > > > > > > > > [4] > > > > > > jakarta.servlet.jsp.jstl > > > > > > jakarta.servlet.jsp.jstl-api > > > > > > 2.0.0 > > > > > > > > > > > > [5] > > > > > > taglibs > > > > > > standard > > > > > > 1.1.2 > > > > > > > > > > > > [6] > > > > > > org.apache.tomee > > > > > > taglibs-shade > > > > > > 9.0.0-M8-SNAPSHOT > > > > > > > > > > > > > > > > > > El mié, 30 mar 2022 a las 1:20, Jean-Louis Monteiro (< > > > > > > jlmonte...@tomitribe.com>) escribió: > > > > > > > > > > > > > Thanks Richard. > > > > > > > > > > > > > > I got personal issues with my computer and it's taking a > > > > > > > bit > > > > > > > of > > > > > > > time to set > > > > > > > everything up again. > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Jean-Louis Monteiro > > > > > > > http://twitter.com/jlouismonteiro > > > > > > > http://www.tomitribe.com
Re: TomEE 9.x - from javax to jakarta namespace
I created https://issues.apache.org/jira/browse/TOMEE-3932 and the PR with the first iteration of the document is ready for review. https://github.com/apache/tomee/pull/878 El sáb, 30 abr 2022 a las 0:26, Zowalla, Richard (< richard.zowa...@hs-heilbronn.de>) escribió: > Sounds good: +1 > > Am Freitag, dem 29.04.2022 um 11:06 +0200 schrieb Jean-Louis Monteiro: > > That sounds great Cesar. Thanks > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Fri, Apr 29, 2022 at 5:48 AM Cesar Hernandez > > > > wrote: > > > > > Thank you for the list, Richard, > > > > > > If there is no objection, I propose to create a > > > https://github.com/apache/tomee/javaxToJakartaNamespace.adoc to > > > keep > > > track > > > of the shaded versions we currently have, common dependencies that > > > will > > > need to be updated, and strategies to troubleshooting common issues > > > and > > > link to the main epic > > > https://issues.apache.org/jira/browse/TOMEE-3862. > > > > > > WDYT? > > > > > > > > > > > > El mié, 27 abr 2022 a las 0:23, Zowalla, Richard (< > > > richard.zowa...@hs-heilbronn.de>) escribió: > > > > > > > Hi, > > > > > > > > I am not aware of any public reference list. There are some > > > > things, > > > > which floated around the mailing list or in the heads, which are: > > > > > > > > - Javamail is currently broken. We need to have a jakarta > > > > compatible > > > > version of Geronimo Javamail. This currently breaks 2 examples > > > > and > > > > prevents platform tck from running. > > > > > > > > - Deltaspike / Kratzo examples require dependency upgrades, i.e. > > > > MVC > > > > 2.0 + Jakarta version of Deltaspike. > > > > > > > > - Micro Profile examples are broken due to the ongoing > > > > integration work > > > > of SmallRye impls. If the integration is done, we can fix them. > > > > > > > > - If Hibernate is used, we either need to upgrade to 6.0.0 _or_ > > > > use the > > > > Jakarta artifact from the 5.6.x series. In some examples, we > > > > still use > > > > Hibernate 4, so the upgrade also requires to deal with > > > > "tomee.jpa.factory.lazy". > > > > > > > > - Check for "http" repositories to avoid the default http blocker > > > > in > > > > newer Maven versions. > > > > > > > > Gruß > > > > Richard > > > > > > > > > > > > Am Dienstag, dem 26.04.2022 um 21:28 -0600 schrieb Cesar > > > > Hernandez: > > > > > Hi all, > > > > > > > > > > Late last week I started to pick and create sub-task related to > > > > > https://issues.apache.org/jira/browse/TOMEE-3862. > > > > > The current CI master status [1] has helped me to identify > > > > > tests that > > > > > need > > > > > fixes, examples that need dependencies updates to match the > > > > > javax. -> > > > > > jakarta , etc. > > > > > > > > > > Do we have a place where we can check the list of knowing-Issue > > > > > and > > > > > knowing-fixes a contributor can take as a reference when trying > > > > > to > > > > > fix a > > > > > subtask from TOMEE-3862 ? > > > > > For example, today I faced a javax/servlet issue [2] that > > > > > required > > > > > some > > > > > dependencies replacements like jstl [3 ] with > > > > > jakarta.servlet.jsp.jstl-api > > > > > [4] and taglibs:standard [5] with taglibs-shade [6]. > > > > > > > > > > > > > > > [1] > > > > > https://ci-builds.apache.org/job/Tomee/job/master-build-full/ > > > > > > > > > > [2] > > > > > > > > > > Caused by: java.lang.NoClassDefFoundError: > > > > > javax/servlet/jsp/tagext/TagSupport > > > > > > > > > > > > > > > [3] > > > > > javax.servlet > > > > > jstl > > > > > 1.1.2 > > > > > > > > > > [4] > > > > > jakarta.servlet.jsp.jstl > > > > > jakarta.servlet.jsp.jstl-api > > > > > 2.0.0 > > > > > > > > > > [5] > > > > > taglibs > > > > > standard > > > > > 1.1.2 > > > > > > > > > > [6] > > > > > org.apache.tomee > > > > > taglibs-shade > > > > > 9.0.0-M8-SNAPSHOT > > > > > > > > > > > > > > > El mié, 30 mar 2022 a las 1:20, Jean-Louis Monteiro (< > > > > > jlmonte...@tomitribe.com>) escribió: > > > > > > > > > > > Thanks Richard. > > > > > > > > > > > > I got personal issues with my computer and it's taking a bit > > > > > > of > > > > > > time to set > > > > > > everything up again. > > > > > > > > > > > > > > > > > > -- > > > > > > Jean-Louis Monteiro > > > > > > http://twitter.com/jlouismonteiro > > > > > > http://www.tomitribe.com > > > > > > > > > > > > > > > > > > On Wed, Mar 30, 2022 at 8:45 AM Zowalla, Richard < > > > > > > richard.zowa...@hs-heilbronn.de> wrote: > > > > > > > > > > > > > Update regarding TOMEE-3879: We were missing --add-opens > > > > > > > options > > > > > > > in the > > > > > > > failover tests to run with Java 11+ - we added it to the > > > > > > > bat / sh > > > > > > > scripts of openejb-standalone. However, bat / sh is not > > > > > > > used in > > > > > > > the > > > > > > > failover tests. > > > > > > > > > > > > > > I added the options in the tests, so TOMEE-3879 is fixed > > > > > > >
Re: TomEE 9.x - from javax to jakarta namespace
Sounds good: +1 Am Freitag, dem 29.04.2022 um 11:06 +0200 schrieb Jean-Louis Monteiro: > That sounds great Cesar. Thanks > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Fri, Apr 29, 2022 at 5:48 AM Cesar Hernandez > > wrote: > > > Thank you for the list, Richard, > > > > If there is no objection, I propose to create a > > https://github.com/apache/tomee/javaxToJakartaNamespace.adoc to > > keep > > track > > of the shaded versions we currently have, common dependencies that > > will > > need to be updated, and strategies to troubleshooting common issues > > and > > link to the main epic > > https://issues.apache.org/jira/browse/TOMEE-3862. > > > > WDYT? > > > > > > > > El mié, 27 abr 2022 a las 0:23, Zowalla, Richard (< > > richard.zowa...@hs-heilbronn.de>) escribió: > > > > > Hi, > > > > > > I am not aware of any public reference list. There are some > > > things, > > > which floated around the mailing list or in the heads, which are: > > > > > > - Javamail is currently broken. We need to have a jakarta > > > compatible > > > version of Geronimo Javamail. This currently breaks 2 examples > > > and > > > prevents platform tck from running. > > > > > > - Deltaspike / Kratzo examples require dependency upgrades, i.e. > > > MVC > > > 2.0 + Jakarta version of Deltaspike. > > > > > > - Micro Profile examples are broken due to the ongoing > > > integration work > > > of SmallRye impls. If the integration is done, we can fix them. > > > > > > - If Hibernate is used, we either need to upgrade to 6.0.0 _or_ > > > use the > > > Jakarta artifact from the 5.6.x series. In some examples, we > > > still use > > > Hibernate 4, so the upgrade also requires to deal with > > > "tomee.jpa.factory.lazy". > > > > > > - Check for "http" repositories to avoid the default http blocker > > > in > > > newer Maven versions. > > > > > > Gruß > > > Richard > > > > > > > > > Am Dienstag, dem 26.04.2022 um 21:28 -0600 schrieb Cesar > > > Hernandez: > > > > Hi all, > > > > > > > > Late last week I started to pick and create sub-task related to > > > > https://issues.apache.org/jira/browse/TOMEE-3862. > > > > The current CI master status [1] has helped me to identify > > > > tests that > > > > need > > > > fixes, examples that need dependencies updates to match the > > > > javax. -> > > > > jakarta , etc. > > > > > > > > Do we have a place where we can check the list of knowing-Issue > > > > and > > > > knowing-fixes a contributor can take as a reference when trying > > > > to > > > > fix a > > > > subtask from TOMEE-3862 ? > > > > For example, today I faced a javax/servlet issue [2] that > > > > required > > > > some > > > > dependencies replacements like jstl [3 ] with > > > > jakarta.servlet.jsp.jstl-api > > > > [4] and taglibs:standard [5] with taglibs-shade [6]. > > > > > > > > > > > > [1] > > > > https://ci-builds.apache.org/job/Tomee/job/master-build-full/ > > > > > > > > [2] > > > > > > > > Caused by: java.lang.NoClassDefFoundError: > > > > javax/servlet/jsp/tagext/TagSupport > > > > > > > > > > > > [3] > > > > javax.servlet > > > > jstl > > > > 1.1.2 > > > > > > > > [4] > > > > jakarta.servlet.jsp.jstl > > > > jakarta.servlet.jsp.jstl-api > > > > 2.0.0 > > > > > > > > [5] > > > > taglibs > > > > standard > > > > 1.1.2 > > > > > > > > [6] > > > > org.apache.tomee > > > > taglibs-shade > > > > 9.0.0-M8-SNAPSHOT > > > > > > > > > > > > El mié, 30 mar 2022 a las 1:20, Jean-Louis Monteiro (< > > > > jlmonte...@tomitribe.com>) escribió: > > > > > > > > > Thanks Richard. > > > > > > > > > > I got personal issues with my computer and it's taking a bit > > > > > of > > > > > time to set > > > > > everything up again. > > > > > > > > > > > > > > > -- > > > > > Jean-Louis Monteiro > > > > > http://twitter.com/jlouismonteiro > > > > > http://www.tomitribe.com > > > > > > > > > > > > > > > On Wed, Mar 30, 2022 at 8:45 AM Zowalla, Richard < > > > > > richard.zowa...@hs-heilbronn.de> wrote: > > > > > > > > > > > Update regarding TOMEE-3879: We were missing --add-opens > > > > > > options > > > > > > in the > > > > > > failover tests to run with Java 11+ - we added it to the > > > > > > bat / sh > > > > > > scripts of openejb-standalone. However, bat / sh is not > > > > > > used in > > > > > > the > > > > > > failover tests. > > > > > > > > > > > > I added the options in the tests, so TOMEE-3879 is fixed > > > > > > now. > > > > > > > > > > > > Gruß > > > > > > Richard > > > > > > > > > > > > Am Dienstag, dem 29.03.2022 um 06:53 + schrieb Zowalla, > > > > > > Richard: > > > > > > > Hi, > > > > > > > > > > > > > > to follow up on TOMEE-3879 [1]: I add some more context > > > > > > > to the > > > > > > > Jira. > > > > > > > The permissions do not matter as we are not invoking the > > > > > > > scripts in > > > > > > > bin/* in the failover itests (itests/failover). > > > > > > > > > > > > > > We are directly booting the servers via the java
Re: TomEE 9.x - from javax to jakarta namespace
That sounds great Cesar. Thanks -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Fri, Apr 29, 2022 at 5:48 AM Cesar Hernandez wrote: > Thank you for the list, Richard, > > If there is no objection, I propose to create a > https://github.com/apache/tomee/javaxToJakartaNamespace.adoc to keep > track > of the shaded versions we currently have, common dependencies that will > need to be updated, and strategies to troubleshooting common issues and > link to the main epic https://issues.apache.org/jira/browse/TOMEE-3862. > > WDYT? > > > > El mié, 27 abr 2022 a las 0:23, Zowalla, Richard (< > richard.zowa...@hs-heilbronn.de>) escribió: > > > Hi, > > > > I am not aware of any public reference list. There are some things, > > which floated around the mailing list or in the heads, which are: > > > > - Javamail is currently broken. We need to have a jakarta compatible > > version of Geronimo Javamail. This currently breaks 2 examples and > > prevents platform tck from running. > > > > - Deltaspike / Kratzo examples require dependency upgrades, i.e. MVC > > 2.0 + Jakarta version of Deltaspike. > > > > - Micro Profile examples are broken due to the ongoing integration work > > of SmallRye impls. If the integration is done, we can fix them. > > > > - If Hibernate is used, we either need to upgrade to 6.0.0 _or_ use the > > Jakarta artifact from the 5.6.x series. In some examples, we still use > > Hibernate 4, so the upgrade also requires to deal with > > "tomee.jpa.factory.lazy". > > > > - Check for "http" repositories to avoid the default http blocker in > > newer Maven versions. > > > > Gruß > > Richard > > > > > > Am Dienstag, dem 26.04.2022 um 21:28 -0600 schrieb Cesar Hernandez: > > > Hi all, > > > > > > Late last week I started to pick and create sub-task related to > > > https://issues.apache.org/jira/browse/TOMEE-3862. > > > The current CI master status [1] has helped me to identify tests that > > > need > > > fixes, examples that need dependencies updates to match the javax. -> > > > jakarta , etc. > > > > > > Do we have a place where we can check the list of knowing-Issue and > > > knowing-fixes a contributor can take as a reference when trying to > > > fix a > > > subtask from TOMEE-3862 ? > > > For example, today I faced a javax/servlet issue [2] that required > > > some > > > dependencies replacements like jstl [3 ] with > > > jakarta.servlet.jsp.jstl-api > > > [4] and taglibs:standard [5] with taglibs-shade [6]. > > > > > > > > > [1] > > > https://ci-builds.apache.org/job/Tomee/job/master-build-full/ > > > > > > [2] > > > > > > Caused by: java.lang.NoClassDefFoundError: > > > javax/servlet/jsp/tagext/TagSupport > > > > > > > > > [3] > > > javax.servlet > > > jstl > > > 1.1.2 > > > > > > [4] > > > jakarta.servlet.jsp.jstl > > > jakarta.servlet.jsp.jstl-api > > > 2.0.0 > > > > > > [5] > > > taglibs > > > standard > > > 1.1.2 > > > > > > [6] > > > org.apache.tomee > > > taglibs-shade > > > 9.0.0-M8-SNAPSHOT > > > > > > > > > El mié, 30 mar 2022 a las 1:20, Jean-Louis Monteiro (< > > > jlmonte...@tomitribe.com>) escribió: > > > > > > > Thanks Richard. > > > > > > > > I got personal issues with my computer and it's taking a bit of > > > > time to set > > > > everything up again. > > > > > > > > > > > > -- > > > > Jean-Louis Monteiro > > > > http://twitter.com/jlouismonteiro > > > > http://www.tomitribe.com > > > > > > > > > > > > On Wed, Mar 30, 2022 at 8:45 AM Zowalla, Richard < > > > > richard.zowa...@hs-heilbronn.de> wrote: > > > > > > > > > Update regarding TOMEE-3879: We were missing --add-opens options > > > > > in the > > > > > failover tests to run with Java 11+ - we added it to the bat / sh > > > > > scripts of openejb-standalone. However, bat / sh is not used in > > > > > the > > > > > failover tests. > > > > > > > > > > I added the options in the tests, so TOMEE-3879 is fixed now. > > > > > > > > > > Gruß > > > > > Richard > > > > > > > > > > Am Dienstag, dem 29.03.2022 um 06:53 + schrieb Zowalla, > > > > > Richard: > > > > > > Hi, > > > > > > > > > > > > to follow up on TOMEE-3879 [1]: I add some more context to the > > > > > > Jira. > > > > > > The permissions do not matter as we are not invoking the > > > > > > scripts in > > > > > > bin/* in the failover itests (itests/failover). > > > > > > > > > > > > We are directly booting the servers via the java command (via > > > > > > Bootstrap > > > > > > from openejb-core) and a lot of properties to configure it, > > > > > > which > > > > > > fails > > > > > > (at least for me atm) with a ClassNotFoundException (see > > > > > > issue). Due > > > > > > to > > > > > > this exception, the servers never become ready and the tests > > > > > > will > > > > > > just > > > > > > timeout. > > > > > > > > > > > > Don't have time to dig into it now but hope it helps anyone, > > > > > > who will > > > > > > work on it in the near future :) > > > > > > > > > > > > Gruß > > > > > > Richard > > > > > > > > > > > > [1]
Re: TomEE 9.x - from javax to jakarta namespace
Thank you for the list, Richard, If there is no objection, I propose to create a https://github.com/apache/tomee/javaxToJakartaNamespace.adoc to keep track of the shaded versions we currently have, common dependencies that will need to be updated, and strategies to troubleshooting common issues and link to the main epic https://issues.apache.org/jira/browse/TOMEE-3862. WDYT? El mié, 27 abr 2022 a las 0:23, Zowalla, Richard (< richard.zowa...@hs-heilbronn.de>) escribió: > Hi, > > I am not aware of any public reference list. There are some things, > which floated around the mailing list or in the heads, which are: > > - Javamail is currently broken. We need to have a jakarta compatible > version of Geronimo Javamail. This currently breaks 2 examples and > prevents platform tck from running. > > - Deltaspike / Kratzo examples require dependency upgrades, i.e. MVC > 2.0 + Jakarta version of Deltaspike. > > - Micro Profile examples are broken due to the ongoing integration work > of SmallRye impls. If the integration is done, we can fix them. > > - If Hibernate is used, we either need to upgrade to 6.0.0 _or_ use the > Jakarta artifact from the 5.6.x series. In some examples, we still use > Hibernate 4, so the upgrade also requires to deal with > "tomee.jpa.factory.lazy". > > - Check for "http" repositories to avoid the default http blocker in > newer Maven versions. > > Gruß > Richard > > > Am Dienstag, dem 26.04.2022 um 21:28 -0600 schrieb Cesar Hernandez: > > Hi all, > > > > Late last week I started to pick and create sub-task related to > > https://issues.apache.org/jira/browse/TOMEE-3862. > > The current CI master status [1] has helped me to identify tests that > > need > > fixes, examples that need dependencies updates to match the javax. -> > > jakarta , etc. > > > > Do we have a place where we can check the list of knowing-Issue and > > knowing-fixes a contributor can take as a reference when trying to > > fix a > > subtask from TOMEE-3862 ? > > For example, today I faced a javax/servlet issue [2] that required > > some > > dependencies replacements like jstl [3 ] with > > jakarta.servlet.jsp.jstl-api > > [4] and taglibs:standard [5] with taglibs-shade [6]. > > > > > > [1] > > https://ci-builds.apache.org/job/Tomee/job/master-build-full/ > > > > [2] > > > > Caused by: java.lang.NoClassDefFoundError: > > javax/servlet/jsp/tagext/TagSupport > > > > > > [3] > > javax.servlet > > jstl > > 1.1.2 > > > > [4] > > jakarta.servlet.jsp.jstl > > jakarta.servlet.jsp.jstl-api > > 2.0.0 > > > > [5] > > taglibs > > standard > > 1.1.2 > > > > [6] > > org.apache.tomee > > taglibs-shade > > 9.0.0-M8-SNAPSHOT > > > > > > El mié, 30 mar 2022 a las 1:20, Jean-Louis Monteiro (< > > jlmonte...@tomitribe.com>) escribió: > > > > > Thanks Richard. > > > > > > I got personal issues with my computer and it's taking a bit of > > > time to set > > > everything up again. > > > > > > > > > -- > > > Jean-Louis Monteiro > > > http://twitter.com/jlouismonteiro > > > http://www.tomitribe.com > > > > > > > > > On Wed, Mar 30, 2022 at 8:45 AM Zowalla, Richard < > > > richard.zowa...@hs-heilbronn.de> wrote: > > > > > > > Update regarding TOMEE-3879: We were missing --add-opens options > > > > in the > > > > failover tests to run with Java 11+ - we added it to the bat / sh > > > > scripts of openejb-standalone. However, bat / sh is not used in > > > > the > > > > failover tests. > > > > > > > > I added the options in the tests, so TOMEE-3879 is fixed now. > > > > > > > > Gruß > > > > Richard > > > > > > > > Am Dienstag, dem 29.03.2022 um 06:53 + schrieb Zowalla, > > > > Richard: > > > > > Hi, > > > > > > > > > > to follow up on TOMEE-3879 [1]: I add some more context to the > > > > > Jira. > > > > > The permissions do not matter as we are not invoking the > > > > > scripts in > > > > > bin/* in the failover itests (itests/failover). > > > > > > > > > > We are directly booting the servers via the java command (via > > > > > Bootstrap > > > > > from openejb-core) and a lot of properties to configure it, > > > > > which > > > > > fails > > > > > (at least for me atm) with a ClassNotFoundException (see > > > > > issue). Due > > > > > to > > > > > this exception, the servers never become ready and the tests > > > > > will > > > > > just > > > > > timeout. > > > > > > > > > > Don't have time to dig into it now but hope it helps anyone, > > > > > who will > > > > > work on it in the near future :) > > > > > > > > > > Gruß > > > > > Richard > > > > > > > > > > [1] https://issues.apache.org/jira/browse/TOMEE-3879 > > > > > > > > > > Am Montag, dem 28.03.2022 um 08:16 + schrieb Zowalla, > > > > > Richard: > > > > > > Heyho, > > > > > > > > > > > > the ZIP created for TOMEE-3879 looks good to me. It has +x > > > > > > set. > > > > > > Perhaps > > > > > > it looses the info during extraction in our code. > > > > > > > > > > > > Can you give a pointer, which tests are suspected to be > > > > > > impacted by > > > > > > it? > > > > > > > >
Re: TomEE 9.x - from javax to jakarta namespace
Hi, I am not aware of any public reference list. There are some things, which floated around the mailing list or in the heads, which are: - Javamail is currently broken. We need to have a jakarta compatible version of Geronimo Javamail. This currently breaks 2 examples and prevents platform tck from running. - Deltaspike / Kratzo examples require dependency upgrades, i.e. MVC 2.0 + Jakarta version of Deltaspike. - Micro Profile examples are broken due to the ongoing integration work of SmallRye impls. If the integration is done, we can fix them. - If Hibernate is used, we either need to upgrade to 6.0.0 _or_ use the Jakarta artifact from the 5.6.x series. In some examples, we still use Hibernate 4, so the upgrade also requires to deal with "tomee.jpa.factory.lazy". - Check for "http" repositories to avoid the default http blocker in newer Maven versions. Gruß Richard Am Dienstag, dem 26.04.2022 um 21:28 -0600 schrieb Cesar Hernandez: > Hi all, > > Late last week I started to pick and create sub-task related to > https://issues.apache.org/jira/browse/TOMEE-3862. > The current CI master status [1] has helped me to identify tests that > need > fixes, examples that need dependencies updates to match the javax. -> > jakarta , etc. > > Do we have a place where we can check the list of knowing-Issue and > knowing-fixes a contributor can take as a reference when trying to > fix a > subtask from TOMEE-3862 ? > For example, today I faced a javax/servlet issue [2] that required > some > dependencies replacements like jstl [3 ] with > jakarta.servlet.jsp.jstl-api > [4] and taglibs:standard [5] with taglibs-shade [6]. > > > [1] > https://ci-builds.apache.org/job/Tomee/job/master-build-full/ > > [2] > > Caused by: java.lang.NoClassDefFoundError: > javax/servlet/jsp/tagext/TagSupport > > > [3] > javax.servlet > jstl > 1.1.2 > > [4] > jakarta.servlet.jsp.jstl > jakarta.servlet.jsp.jstl-api > 2.0.0 > > [5] > taglibs > standard > 1.1.2 > > [6] > org.apache.tomee > taglibs-shade > 9.0.0-M8-SNAPSHOT > > > El mié, 30 mar 2022 a las 1:20, Jean-Louis Monteiro (< > jlmonte...@tomitribe.com>) escribió: > > > Thanks Richard. > > > > I got personal issues with my computer and it's taking a bit of > > time to set > > everything up again. > > > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Wed, Mar 30, 2022 at 8:45 AM Zowalla, Richard < > > richard.zowa...@hs-heilbronn.de> wrote: > > > > > Update regarding TOMEE-3879: We were missing --add-opens options > > > in the > > > failover tests to run with Java 11+ - we added it to the bat / sh > > > scripts of openejb-standalone. However, bat / sh is not used in > > > the > > > failover tests. > > > > > > I added the options in the tests, so TOMEE-3879 is fixed now. > > > > > > Gruß > > > Richard > > > > > > Am Dienstag, dem 29.03.2022 um 06:53 + schrieb Zowalla, > > > Richard: > > > > Hi, > > > > > > > > to follow up on TOMEE-3879 [1]: I add some more context to the > > > > Jira. > > > > The permissions do not matter as we are not invoking the > > > > scripts in > > > > bin/* in the failover itests (itests/failover). > > > > > > > > We are directly booting the servers via the java command (via > > > > Bootstrap > > > > from openejb-core) and a lot of properties to configure it, > > > > which > > > > fails > > > > (at least for me atm) with a ClassNotFoundException (see > > > > issue). Due > > > > to > > > > this exception, the servers never become ready and the tests > > > > will > > > > just > > > > timeout. > > > > > > > > Don't have time to dig into it now but hope it helps anyone, > > > > who will > > > > work on it in the near future :) > > > > > > > > Gruß > > > > Richard > > > > > > > > [1] https://issues.apache.org/jira/browse/TOMEE-3879 > > > > > > > > Am Montag, dem 28.03.2022 um 08:16 + schrieb Zowalla, > > > > Richard: > > > > > Heyho, > > > > > > > > > > the ZIP created for TOMEE-3879 looks good to me. It has +x > > > > > set. > > > > > Perhaps > > > > > it looses the info during extraction in our code. > > > > > > > > > > Can you give a pointer, which tests are suspected to be > > > > > impacted by > > > > > it? > > > > > > > > > > Gruß > > > > > Richard > > > > > > > > > > Am Samstag, dem 26.03.2022 um 10:40 +0100 schrieb Jean-Louis > > > > > Monteiro: > > > > > > Awesome, divide and conquer. > > > > > > > > > > > > Trying to add a bit more... > > > > > > This one might be small for someone with some spare cycles. > > > > > > > > > > > > https://issues.apache.org/jira/browse/TOMEE-3879 > > > > > > > > > > > > > > > > > > -- > > > > > > Jean-Louis Monteiro > > > > > > http://twitter.com/jlouismonteiro > > > > > > http://www.tomitribe.com > > > > > > > > > > > > > > > > > > On Sat, Mar 26, 2022 at 5:35 AM David Blevins < > > > > > > david.blev...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > > On Mar 24, 2022, at 2:28 AM, Jean-Louis
Re: TomEE 9.x - from javax to jakarta namespace
Hi all, Late last week I started to pick and create sub-task related to https://issues.apache.org/jira/browse/TOMEE-3862. The current CI master status [1] has helped me to identify tests that need fixes, examples that need dependencies updates to match the javax. -> jakarta , etc. Do we have a place where we can check the list of knowing-Issue and knowing-fixes a contributor can take as a reference when trying to fix a subtask from TOMEE-3862 ? For example, today I faced a javax/servlet issue [2] that required some dependencies replacements like jstl [3 ] with jakarta.servlet.jsp.jstl-api [4] and taglibs:standard [5] with taglibs-shade [6]. [1] https://ci-builds.apache.org/job/Tomee/job/master-build-full/ [2] Caused by: java.lang.NoClassDefFoundError: javax/servlet/jsp/tagext/TagSupport [3] javax.servlet jstl 1.1.2 [4] jakarta.servlet.jsp.jstl jakarta.servlet.jsp.jstl-api 2.0.0 [5] taglibs standard 1.1.2 [6] org.apache.tomee taglibs-shade 9.0.0-M8-SNAPSHOT El mié, 30 mar 2022 a las 1:20, Jean-Louis Monteiro (< jlmonte...@tomitribe.com>) escribió: > Thanks Richard. > > I got personal issues with my computer and it's taking a bit of time to set > everything up again. > > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Wed, Mar 30, 2022 at 8:45 AM Zowalla, Richard < > richard.zowa...@hs-heilbronn.de> wrote: > > > Update regarding TOMEE-3879: We were missing --add-opens options in the > > failover tests to run with Java 11+ - we added it to the bat / sh > > scripts of openejb-standalone. However, bat / sh is not used in the > > failover tests. > > > > I added the options in the tests, so TOMEE-3879 is fixed now. > > > > Gruß > > Richard > > > > Am Dienstag, dem 29.03.2022 um 06:53 + schrieb Zowalla, Richard: > > > Hi, > > > > > > to follow up on TOMEE-3879 [1]: I add some more context to the Jira. > > > The permissions do not matter as we are not invoking the scripts in > > > bin/* in the failover itests (itests/failover). > > > > > > We are directly booting the servers via the java command (via > > > Bootstrap > > > from openejb-core) and a lot of properties to configure it, which > > > fails > > > (at least for me atm) with a ClassNotFoundException (see issue). Due > > > to > > > this exception, the servers never become ready and the tests will > > > just > > > timeout. > > > > > > Don't have time to dig into it now but hope it helps anyone, who will > > > work on it in the near future :) > > > > > > Gruß > > > Richard > > > > > > [1] https://issues.apache.org/jira/browse/TOMEE-3879 > > > > > > Am Montag, dem 28.03.2022 um 08:16 + schrieb Zowalla, Richard: > > > > Heyho, > > > > > > > > the ZIP created for TOMEE-3879 looks good to me. It has +x set. > > > > Perhaps > > > > it looses the info during extraction in our code. > > > > > > > > Can you give a pointer, which tests are suspected to be impacted by > > > > it? > > > > > > > > Gruß > > > > Richard > > > > > > > > Am Samstag, dem 26.03.2022 um 10:40 +0100 schrieb Jean-Louis > > > > Monteiro: > > > > > Awesome, divide and conquer. > > > > > > > > > > Trying to add a bit more... > > > > > This one might be small for someone with some spare cycles. > > > > > > > > > > https://issues.apache.org/jira/browse/TOMEE-3879 > > > > > > > > > > > > > > > -- > > > > > Jean-Louis Monteiro > > > > > http://twitter.com/jlouismonteiro > > > > > http://www.tomitribe.com > > > > > > > > > > > > > > > On Sat, Mar 26, 2022 at 5:35 AM David Blevins < > > > > > david.blev...@gmail.com> > > > > > wrote: > > > > > > > > > > > > On Mar 24, 2022, at 2:28 AM, Jean-Louis Monteiro < > > > > > > jlmonte...@tomitribe.com> wrote: > > > > > > > We can now divide and conquer. An issue has been created > > > > > > > https://issues.apache.org/jira/browse/TOMEE-3862 > > > > > > > We are going to add as many small tasks as possible so people > > > > > > > can > > > > > > > pick > > > > > > and > > > > > > > contribute in parallel. > > > > > > > > > > > > Thanks for that JIRA. I saw an easy one I could do and went a > > > > > > head > > > > > > and > > > > > > knocked it out :) > > > > > > > > > > > > - > > > > > > > > > https://github.com/apache/tomee/commit/6e37ec02ca60fe955a3a909d761e09aa5a506978 > > > > > > > > > > > > That yanks 1 minute out of the build on my machine. > > > > > > > > > > > > > > > > > > -David > > > > > > > > > > > > > > > > > > > On Tue, Mar 22, 2022 at 1:59 PM Jean-Louis Monteiro < > > > > > > > jlmonte...@tomitribe.com> wrote: > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > I've been working for quite a long time on TomEE 9.x, and > > > > > > > > it's > > > > > > > > been more > > > > > > > > challenging and painful than I was expecting. I thought it > > > > > > > > would be > > > > > > good to > > > > > > > > give you some sort of status. > > > > > > > > > > > > > > > > I created a PR for the work. As a reminder, since Java EE > > > > > > > > moved > > > > > > > > to > > > >
Re: TomEE 9.x - from javax to jakarta namespace
Thanks Richard. I got personal issues with my computer and it's taking a bit of time to set everything up again. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Wed, Mar 30, 2022 at 8:45 AM Zowalla, Richard < richard.zowa...@hs-heilbronn.de> wrote: > Update regarding TOMEE-3879: We were missing --add-opens options in the > failover tests to run with Java 11+ - we added it to the bat / sh > scripts of openejb-standalone. However, bat / sh is not used in the > failover tests. > > I added the options in the tests, so TOMEE-3879 is fixed now. > > Gruß > Richard > > Am Dienstag, dem 29.03.2022 um 06:53 + schrieb Zowalla, Richard: > > Hi, > > > > to follow up on TOMEE-3879 [1]: I add some more context to the Jira. > > The permissions do not matter as we are not invoking the scripts in > > bin/* in the failover itests (itests/failover). > > > > We are directly booting the servers via the java command (via > > Bootstrap > > from openejb-core) and a lot of properties to configure it, which > > fails > > (at least for me atm) with a ClassNotFoundException (see issue). Due > > to > > this exception, the servers never become ready and the tests will > > just > > timeout. > > > > Don't have time to dig into it now but hope it helps anyone, who will > > work on it in the near future :) > > > > Gruß > > Richard > > > > [1] https://issues.apache.org/jira/browse/TOMEE-3879 > > > > Am Montag, dem 28.03.2022 um 08:16 + schrieb Zowalla, Richard: > > > Heyho, > > > > > > the ZIP created for TOMEE-3879 looks good to me. It has +x set. > > > Perhaps > > > it looses the info during extraction in our code. > > > > > > Can you give a pointer, which tests are suspected to be impacted by > > > it? > > > > > > Gruß > > > Richard > > > > > > Am Samstag, dem 26.03.2022 um 10:40 +0100 schrieb Jean-Louis > > > Monteiro: > > > > Awesome, divide and conquer. > > > > > > > > Trying to add a bit more... > > > > This one might be small for someone with some spare cycles. > > > > > > > > https://issues.apache.org/jira/browse/TOMEE-3879 > > > > > > > > > > > > -- > > > > Jean-Louis Monteiro > > > > http://twitter.com/jlouismonteiro > > > > http://www.tomitribe.com > > > > > > > > > > > > On Sat, Mar 26, 2022 at 5:35 AM David Blevins < > > > > david.blev...@gmail.com> > > > > wrote: > > > > > > > > > > On Mar 24, 2022, at 2:28 AM, Jean-Louis Monteiro < > > > > > jlmonte...@tomitribe.com> wrote: > > > > > > We can now divide and conquer. An issue has been created > > > > > > https://issues.apache.org/jira/browse/TOMEE-3862 > > > > > > We are going to add as many small tasks as possible so people > > > > > > can > > > > > > pick > > > > > and > > > > > > contribute in parallel. > > > > > > > > > > Thanks for that JIRA. I saw an easy one I could do and went a > > > > > head > > > > > and > > > > > knocked it out :) > > > > > > > > > > - > > > > > > https://github.com/apache/tomee/commit/6e37ec02ca60fe955a3a909d761e09aa5a506978 > > > > > > > > > > That yanks 1 minute out of the build on my machine. > > > > > > > > > > > > > > > -David > > > > > > > > > > > > > > > > On Tue, Mar 22, 2022 at 1:59 PM Jean-Louis Monteiro < > > > > > > jlmonte...@tomitribe.com> wrote: > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > I've been working for quite a long time on TomEE 9.x, and > > > > > > > it's > > > > > > > been more > > > > > > > challenging and painful than I was expecting. I thought it > > > > > > > would be > > > > > good to > > > > > > > give you some sort of status. > > > > > > > > > > > > > > I created a PR for the work. As a reminder, since Java EE > > > > > > > moved > > > > > > > to > > > > > Eclipse > > > > > > > to become Jakarta EE, we had a switch from javax.* > > > > > > > namespace > > > > > > > to > > > > > jakarta.* > > > > > > > namespace. This is an impacting change, since all > > > > > > > applications > > > > > > > and > > > > > > > applications servers are built on top of it. > > > > > > > > > > > > > > In TomEE, we decided to do that change in TomEE. We had > > > > > > > previously a > > > > > > > bytecode change approach like an application could do. It > > > > > > > worked and we > > > > > > > were able to get certified. But it had a lot of > > > > > > > limitations, > > > > > > > so > > > > > > > we had > > > > > to > > > > > > > do the migration in the code and fix all compatibility > > > > > > > issues. > > > > > > > > > > > > > > Here is the PR https://github.com/apache/tomee/pull/814 > > > > > > > It has 90+ commits and nearly 5000 files touched (added, > > > > > > > removed, > > > > > > > updated). I understand it's a lot and it makes it almost > > > > > > > impossible to > > > > > > > review. But I did not see much approaches in this scenario > > > > > > > to > > > > > > > create > > > > > > > smaller PRs. > > > > > > > > > > > > > > I created a Jenkins build though available at > > > > > > > > https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/ >
Re: TomEE 9.x - from javax to jakarta namespace
Update regarding TOMEE-3879: We were missing --add-opens options in the failover tests to run with Java 11+ - we added it to the bat / sh scripts of openejb-standalone. However, bat / sh is not used in the failover tests. I added the options in the tests, so TOMEE-3879 is fixed now. Gruß Richard Am Dienstag, dem 29.03.2022 um 06:53 + schrieb Zowalla, Richard: > Hi, > > to follow up on TOMEE-3879 [1]: I add some more context to the Jira. > The permissions do not matter as we are not invoking the scripts in > bin/* in the failover itests (itests/failover). > > We are directly booting the servers via the java command (via > Bootstrap > from openejb-core) and a lot of properties to configure it, which > fails > (at least for me atm) with a ClassNotFoundException (see issue). Due > to > this exception, the servers never become ready and the tests will > just > timeout. > > Don't have time to dig into it now but hope it helps anyone, who will > work on it in the near future :) > > Gruß > Richard > > [1] https://issues.apache.org/jira/browse/TOMEE-3879 > > Am Montag, dem 28.03.2022 um 08:16 + schrieb Zowalla, Richard: > > Heyho, > > > > the ZIP created for TOMEE-3879 looks good to me. It has +x set. > > Perhaps > > it looses the info during extraction in our code. > > > > Can you give a pointer, which tests are suspected to be impacted by > > it? > > > > Gruß > > Richard > > > > Am Samstag, dem 26.03.2022 um 10:40 +0100 schrieb Jean-Louis > > Monteiro: > > > Awesome, divide and conquer. > > > > > > Trying to add a bit more... > > > This one might be small for someone with some spare cycles. > > > > > > https://issues.apache.org/jira/browse/TOMEE-3879 > > > > > > > > > -- > > > Jean-Louis Monteiro > > > http://twitter.com/jlouismonteiro > > > http://www.tomitribe.com > > > > > > > > > On Sat, Mar 26, 2022 at 5:35 AM David Blevins < > > > david.blev...@gmail.com> > > > wrote: > > > > > > > > On Mar 24, 2022, at 2:28 AM, Jean-Louis Monteiro < > > > > jlmonte...@tomitribe.com> wrote: > > > > > We can now divide and conquer. An issue has been created > > > > > https://issues.apache.org/jira/browse/TOMEE-3862 > > > > > We are going to add as many small tasks as possible so people > > > > > can > > > > > pick > > > > and > > > > > contribute in parallel. > > > > > > > > Thanks for that JIRA. I saw an easy one I could do and went a > > > > head > > > > and > > > > knocked it out :) > > > > > > > > - > > > > https://github.com/apache/tomee/commit/6e37ec02ca60fe955a3a909d761e09aa5a506978 > > > > > > > > That yanks 1 minute out of the build on my machine. > > > > > > > > > > > > -David > > > > > > > > > > > > > On Tue, Mar 22, 2022 at 1:59 PM Jean-Louis Monteiro < > > > > > jlmonte...@tomitribe.com> wrote: > > > > > > > > > > > Hi, > > > > > > > > > > > > I've been working for quite a long time on TomEE 9.x, and > > > > > > it's > > > > > > been more > > > > > > challenging and painful than I was expecting. I thought it > > > > > > would be > > > > good to > > > > > > give you some sort of status. > > > > > > > > > > > > I created a PR for the work. As a reminder, since Java EE > > > > > > moved > > > > > > to > > > > Eclipse > > > > > > to become Jakarta EE, we had a switch from javax.* > > > > > > namespace > > > > > > to > > > > jakarta.* > > > > > > namespace. This is an impacting change, since all > > > > > > applications > > > > > > and > > > > > > applications servers are built on top of it. > > > > > > > > > > > > In TomEE, we decided to do that change in TomEE. We had > > > > > > previously a > > > > > > bytecode change approach like an application could do. It > > > > > > worked and we > > > > > > were able to get certified. But it had a lot of > > > > > > limitations, > > > > > > so > > > > > > we had > > > > to > > > > > > do the migration in the code and fix all compatibility > > > > > > issues. > > > > > > > > > > > > Here is the PR https://github.com/apache/tomee/pull/814 > > > > > > It has 90+ commits and nearly 5000 files touched (added, > > > > > > removed, > > > > > > updated). I understand it's a lot and it makes it almost > > > > > > impossible to > > > > > > review. But I did not see much approaches in this scenario > > > > > > to > > > > > > create > > > > > > smaller PRs. > > > > > > > > > > > > I created a Jenkins build though available at > > > > > > https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/ > > > > > > > > > > > > It makes it possible to track the progress. There have been > > > > > > steps > > > > forward > > > > > > and steps backward. > > > > > > > > > > > > All the code does not sit under TomEE, we use a bunch of > > > > > > third > > > > > > party > > > > > > projects and libraries. I have been able to contribute, > > > > > > publish > > > > > > jakarta > > > > > > compatible versions and get releases for some of them > > > > > > (Jakarta > > > > > > EE APIs > > > > Uber > > > > > > jar, Geronimo Connectors and
Re: TomEE 9.x - from javax to jakarta namespace
Hi, to follow up on TOMEE-3879 [1]: I add some more context to the Jira. The permissions do not matter as we are not invoking the scripts in bin/* in the failover itests (itests/failover). We are directly booting the servers via the java command (via Bootstrap from openejb-core) and a lot of properties to configure it, which fails (at least for me atm) with a ClassNotFoundException (see issue). Due to this exception, the servers never become ready and the tests will just timeout. Don't have time to dig into it now but hope it helps anyone, who will work on it in the near future :) Gruß Richard [1] https://issues.apache.org/jira/browse/TOMEE-3879 Am Montag, dem 28.03.2022 um 08:16 + schrieb Zowalla, Richard: > Heyho, > > the ZIP created for TOMEE-3879 looks good to me. It has +x set. > Perhaps > it looses the info during extraction in our code. > > Can you give a pointer, which tests are suspected to be impacted by > it? > > Gruß > Richard > > Am Samstag, dem 26.03.2022 um 10:40 +0100 schrieb Jean-Louis > Monteiro: > > Awesome, divide and conquer. > > > > Trying to add a bit more... > > This one might be small for someone with some spare cycles. > > > > https://issues.apache.org/jira/browse/TOMEE-3879 > > > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Sat, Mar 26, 2022 at 5:35 AM David Blevins < > > david.blev...@gmail.com> > > wrote: > > > > > > On Mar 24, 2022, at 2:28 AM, Jean-Louis Monteiro < > > > jlmonte...@tomitribe.com> wrote: > > > > We can now divide and conquer. An issue has been created > > > > https://issues.apache.org/jira/browse/TOMEE-3862 > > > > We are going to add as many small tasks as possible so people > > > > can > > > > pick > > > and > > > > contribute in parallel. > > > > > > Thanks for that JIRA. I saw an easy one I could do and went a > > > head > > > and > > > knocked it out :) > > > > > > - > > > https://github.com/apache/tomee/commit/6e37ec02ca60fe955a3a909d761e09aa5a506978 > > > > > > That yanks 1 minute out of the build on my machine. > > > > > > > > > -David > > > > > > > > > > On Tue, Mar 22, 2022 at 1:59 PM Jean-Louis Monteiro < > > > > jlmonte...@tomitribe.com> wrote: > > > > > > > > > Hi, > > > > > > > > > > I've been working for quite a long time on TomEE 9.x, and > > > > > it's > > > > > been more > > > > > challenging and painful than I was expecting. I thought it > > > > > would be > > > good to > > > > > give you some sort of status. > > > > > > > > > > I created a PR for the work. As a reminder, since Java EE > > > > > moved > > > > > to > > > Eclipse > > > > > to become Jakarta EE, we had a switch from javax.* namespace > > > > > to > > > jakarta.* > > > > > namespace. This is an impacting change, since all > > > > > applications > > > > > and > > > > > applications servers are built on top of it. > > > > > > > > > > In TomEE, we decided to do that change in TomEE. We had > > > > > previously a > > > > > bytecode change approach like an application could do. It > > > > > worked and we > > > > > were able to get certified. But it had a lot of limitations, > > > > > so > > > > > we had > > > to > > > > > do the migration in the code and fix all compatibility > > > > > issues. > > > > > > > > > > Here is the PR https://github.com/apache/tomee/pull/814 > > > > > It has 90+ commits and nearly 5000 files touched (added, > > > > > removed, > > > > > updated). I understand it's a lot and it makes it almost > > > > > impossible to > > > > > review. But I did not see much approaches in this scenario to > > > > > create > > > > > smaller PRs. > > > > > > > > > > I created a Jenkins build though available at > > > > > https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/ > > > > > > > > > > It makes it possible to track the progress. There have been > > > > > steps > > > forward > > > > > and steps backward. > > > > > > > > > > All the code does not sit under TomEE, we use a bunch of > > > > > third > > > > > party > > > > > projects and libraries. I have been able to contribute, > > > > > publish > > > > > jakarta > > > > > compatible versions and get releases for some of them > > > > > (Jakarta > > > > > EE APIs > > > Uber > > > > > jar, Geronimo Connectors and Transaction Manager, Geronimo > > > > > Config, > > > Health, > > > > > Metrics, OpenTracing, OpenAPI. OpenJPA, BVal, and > > > > > OpenWebBeans > > > > > will be > > > > > released soon. > > > > > > > > > > The big parts is CXF, and ActiveMQ. I had to get them done in > > > > > TomEE and > > > > > update all group/artifact ids. It's under deps, alongside > > > > > with > > > > > SXC, > > > DBCP, > > > > > and others. > > > > > > > > > > In terms of removal, I tried to remove old stuff like SAAJ > > > > > Axis > > > > > 1 > > > > > integration, JAX RPC, Management J2EE and a couple of other > > > > > old > > > > > things. > > > > > > > > > > A lot of other libraries got updated to their
Re: TomEE 9.x - from javax to jakarta namespace
Heyho, the ZIP created for TOMEE-3879 looks good to me. It has +x set. Perhaps it looses the info during extraction in our code. Can you give a pointer, which tests are suspected to be impacted by it? Gruß Richard Am Samstag, dem 26.03.2022 um 10:40 +0100 schrieb Jean-Louis Monteiro: > Awesome, divide and conquer. > > Trying to add a bit more... > This one might be small for someone with some spare cycles. > > https://issues.apache.org/jira/browse/TOMEE-3879 > > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Sat, Mar 26, 2022 at 5:35 AM David Blevins < > david.blev...@gmail.com> > wrote: > > > > On Mar 24, 2022, at 2:28 AM, Jean-Louis Monteiro < > > jlmonte...@tomitribe.com> wrote: > > > We can now divide and conquer. An issue has been created > > > https://issues.apache.org/jira/browse/TOMEE-3862 > > > We are going to add as many small tasks as possible so people can > > > pick > > and > > > contribute in parallel. > > > > Thanks for that JIRA. I saw an easy one I could do and went a head > > and > > knocked it out :) > > > > - > > https://github.com/apache/tomee/commit/6e37ec02ca60fe955a3a909d761e09aa5a506978 > > > > That yanks 1 minute out of the build on my machine. > > > > > > -David > > > > > > > On Tue, Mar 22, 2022 at 1:59 PM Jean-Louis Monteiro < > > > jlmonte...@tomitribe.com> wrote: > > > > > > > Hi, > > > > > > > > I've been working for quite a long time on TomEE 9.x, and it's > > > > been more > > > > challenging and painful than I was expecting. I thought it > > > > would be > > good to > > > > give you some sort of status. > > > > > > > > I created a PR for the work. As a reminder, since Java EE moved > > > > to > > Eclipse > > > > to become Jakarta EE, we had a switch from javax.* namespace to > > jakarta.* > > > > namespace. This is an impacting change, since all applications > > > > and > > > > applications servers are built on top of it. > > > > > > > > In TomEE, we decided to do that change in TomEE. We had > > > > previously a > > > > bytecode change approach like an application could do. It > > > > worked and we > > > > were able to get certified. But it had a lot of limitations, so > > > > we had > > to > > > > do the migration in the code and fix all compatibility issues. > > > > > > > > Here is the PR https://github.com/apache/tomee/pull/814 > > > > It has 90+ commits and nearly 5000 files touched (added, > > > > removed, > > > > updated). I understand it's a lot and it makes it almost > > > > impossible to > > > > review. But I did not see much approaches in this scenario to > > > > create > > > > smaller PRs. > > > > > > > > I created a Jenkins build though available at > > > > https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/ > > > > > > > > It makes it possible to track the progress. There have been > > > > steps > > forward > > > > and steps backward. > > > > > > > > All the code does not sit under TomEE, we use a bunch of third > > > > party > > > > projects and libraries. I have been able to contribute, publish > > > > jakarta > > > > compatible versions and get releases for some of them (Jakarta > > > > EE APIs > > Uber > > > > jar, Geronimo Connectors and Transaction Manager, Geronimo > > > > Config, > > Health, > > > > Metrics, OpenTracing, OpenAPI. OpenJPA, BVal, and OpenWebBeans > > > > will be > > > > released soon. > > > > > > > > The big parts is CXF, and ActiveMQ. I had to get them done in > > > > TomEE and > > > > update all group/artifact ids. It's under deps, alongside with > > > > SXC, > > DBCP, > > > > and others. > > > > > > > > In terms of removal, I tried to remove old stuff like SAAJ Axis > > > > 1 > > > > integration, JAX RPC, Management J2EE and a couple of other old > > > > things. > > > > > > > > A lot of other libraries got updated to their latest version > > > > when > > > > available in the new jakarta namespace. > > > > > > > > I'm starting to get all the build stable and many modules are > > > > passing > > now, > > > > including all CXF webservices, OpenEJB Core, and others. I can > > > > get a > > build > > > > and run TomEE. > > > > > > > > Goal is to get a green build asap so we can start working on > > > > TCK. > > > > The "quick" build is now green. Working on the full build. > > > > > > > > I'll soon be creating a branch for TomEE 8.x maintenance and > > > > merge the > > PR. > > > > I'm hoping we can then have small PRs or at least more people > > > > working in > > > > parallel. > > > > > > > > -- > > > > Jean-Louis Monteiro > > > > http://twitter.com/jlouismonteiro > > > > http://www.tomitribe.com > > > > smime.p7s Description: S/MIME cryptographic signature
Re: TomEE 9.x - from javax to jakarta namespace
Awesome, divide and conquer. Trying to add a bit more... This one might be small for someone with some spare cycles. https://issues.apache.org/jira/browse/TOMEE-3879 -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Sat, Mar 26, 2022 at 5:35 AM David Blevins wrote: > > On Mar 24, 2022, at 2:28 AM, Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > > > > We can now divide and conquer. An issue has been created > > https://issues.apache.org/jira/browse/TOMEE-3862 > > We are going to add as many small tasks as possible so people can pick > and > > contribute in parallel. > > Thanks for that JIRA. I saw an easy one I could do and went a head and > knocked it out :) > > - > https://github.com/apache/tomee/commit/6e37ec02ca60fe955a3a909d761e09aa5a506978 > > That yanks 1 minute out of the build on my machine. > > > -David > > > > > > On Tue, Mar 22, 2022 at 1:59 PM Jean-Louis Monteiro < > > jlmonte...@tomitribe.com> wrote: > > > >> Hi, > >> > >> I've been working for quite a long time on TomEE 9.x, and it's been more > >> challenging and painful than I was expecting. I thought it would be > good to > >> give you some sort of status. > >> > >> I created a PR for the work. As a reminder, since Java EE moved to > Eclipse > >> to become Jakarta EE, we had a switch from javax.* namespace to > jakarta.* > >> namespace. This is an impacting change, since all applications and > >> applications servers are built on top of it. > >> > >> In TomEE, we decided to do that change in TomEE. We had previously a > >> bytecode change approach like an application could do. It worked and we > >> were able to get certified. But it had a lot of limitations, so we had > to > >> do the migration in the code and fix all compatibility issues. > >> > >> Here is the PR https://github.com/apache/tomee/pull/814 > >> It has 90+ commits and nearly 5000 files touched (added, removed, > >> updated). I understand it's a lot and it makes it almost impossible to > >> review. But I did not see much approaches in this scenario to create > >> smaller PRs. > >> > >> I created a Jenkins build though available at > >> https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/ > >> > >> It makes it possible to track the progress. There have been steps > forward > >> and steps backward. > >> > >> All the code does not sit under TomEE, we use a bunch of third party > >> projects and libraries. I have been able to contribute, publish jakarta > >> compatible versions and get releases for some of them (Jakarta EE APIs > Uber > >> jar, Geronimo Connectors and Transaction Manager, Geronimo Config, > Health, > >> Metrics, OpenTracing, OpenAPI. OpenJPA, BVal, and OpenWebBeans will be > >> released soon. > >> > >> The big parts is CXF, and ActiveMQ. I had to get them done in TomEE and > >> update all group/artifact ids. It's under deps, alongside with SXC, > DBCP, > >> and others. > >> > >> In terms of removal, I tried to remove old stuff like SAAJ Axis 1 > >> integration, JAX RPC, Management J2EE and a couple of other old things. > >> > >> A lot of other libraries got updated to their latest version when > >> available in the new jakarta namespace. > >> > >> I'm starting to get all the build stable and many modules are passing > now, > >> including all CXF webservices, OpenEJB Core, and others. I can get a > build > >> and run TomEE. > >> > >> Goal is to get a green build asap so we can start working on TCK. > >> The "quick" build is now green. Working on the full build. > >> > >> I'll soon be creating a branch for TomEE 8.x maintenance and merge the > PR. > >> I'm hoping we can then have small PRs or at least more people working in > >> parallel. > >> > >> -- > >> Jean-Louis Monteiro > >> http://twitter.com/jlouismonteiro > >> http://www.tomitribe.com > >> > >
Re: TomEE 9.x - from javax to jakarta namespace
> On Mar 24, 2022, at 2:28 AM, Jean-Louis Monteiro > wrote: > > We can now divide and conquer. An issue has been created > https://issues.apache.org/jira/browse/TOMEE-3862 > We are going to add as many small tasks as possible so people can pick and > contribute in parallel. Thanks for that JIRA. I saw an easy one I could do and went a head and knocked it out :) - https://github.com/apache/tomee/commit/6e37ec02ca60fe955a3a909d761e09aa5a506978 That yanks 1 minute out of the build on my machine. -David > > On Tue, Mar 22, 2022 at 1:59 PM Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > >> Hi, >> >> I've been working for quite a long time on TomEE 9.x, and it's been more >> challenging and painful than I was expecting. I thought it would be good to >> give you some sort of status. >> >> I created a PR for the work. As a reminder, since Java EE moved to Eclipse >> to become Jakarta EE, we had a switch from javax.* namespace to jakarta.* >> namespace. This is an impacting change, since all applications and >> applications servers are built on top of it. >> >> In TomEE, we decided to do that change in TomEE. We had previously a >> bytecode change approach like an application could do. It worked and we >> were able to get certified. But it had a lot of limitations, so we had to >> do the migration in the code and fix all compatibility issues. >> >> Here is the PR https://github.com/apache/tomee/pull/814 >> It has 90+ commits and nearly 5000 files touched (added, removed, >> updated). I understand it's a lot and it makes it almost impossible to >> review. But I did not see much approaches in this scenario to create >> smaller PRs. >> >> I created a Jenkins build though available at >> https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/ >> >> It makes it possible to track the progress. There have been steps forward >> and steps backward. >> >> All the code does not sit under TomEE, we use a bunch of third party >> projects and libraries. I have been able to contribute, publish jakarta >> compatible versions and get releases for some of them (Jakarta EE APIs Uber >> jar, Geronimo Connectors and Transaction Manager, Geronimo Config, Health, >> Metrics, OpenTracing, OpenAPI. OpenJPA, BVal, and OpenWebBeans will be >> released soon. >> >> The big parts is CXF, and ActiveMQ. I had to get them done in TomEE and >> update all group/artifact ids. It's under deps, alongside with SXC, DBCP, >> and others. >> >> In terms of removal, I tried to remove old stuff like SAAJ Axis 1 >> integration, JAX RPC, Management J2EE and a couple of other old things. >> >> A lot of other libraries got updated to their latest version when >> available in the new jakarta namespace. >> >> I'm starting to get all the build stable and many modules are passing now, >> including all CXF webservices, OpenEJB Core, and others. I can get a build >> and run TomEE. >> >> Goal is to get a green build asap so we can start working on TCK. >> The "quick" build is now green. Working on the full build. >> >> I'll soon be creating a branch for TomEE 8.x maintenance and merge the PR. >> I'm hoping we can then have small PRs or at least more people working in >> parallel. >> >> -- >> Jean-Louis Monteiro >> http://twitter.com/jlouismonteiro >> http://www.tomitribe.com >> smime.p7s Description: S/MIME cryptographic signature
Re: TomEE 9.x - from javax to jakarta namespace
Hi, Some additional notes based on current progress. We have successfully created a maintenance branch for TomEE 8.x with all associated builds on Jenkins. We have been able to stabilize the work for TomEE 9.x on the PR and therefore we merged it to master which is now our main development branch. The quick build is green but the full build still has a lot of test failures. Same as for TCK the first iterations make it possible to significantly drop the number of failures. The remaining failures are usually harder to fix. We can now divide and conquer. An issue has been created https://issues.apache.org/jira/browse/TOMEE-3862 We are going to add as many small tasks as possible so people can pick and contribute in parallel. Thanks a lot Richard for all the hard work -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, Mar 22, 2022 at 1:59 PM Jean-Louis Monteiro < jlmonte...@tomitribe.com> wrote: > Hi, > > I've been working for quite a long time on TomEE 9.x, and it's been more > challenging and painful than I was expecting. I thought it would be good to > give you some sort of status. > > I created a PR for the work. As a reminder, since Java EE moved to Eclipse > to become Jakarta EE, we had a switch from javax.* namespace to jakarta.* > namespace. This is an impacting change, since all applications and > applications servers are built on top of it. > > In TomEE, we decided to do that change in TomEE. We had previously a > bytecode change approach like an application could do. It worked and we > were able to get certified. But it had a lot of limitations, so we had to > do the migration in the code and fix all compatibility issues. > > Here is the PR https://github.com/apache/tomee/pull/814 > It has 90+ commits and nearly 5000 files touched (added, removed, > updated). I understand it's a lot and it makes it almost impossible to > review. But I did not see much approaches in this scenario to create > smaller PRs. > > I created a Jenkins build though available at > https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/ > > It makes it possible to track the progress. There have been steps forward > and steps backward. > > All the code does not sit under TomEE, we use a bunch of third party > projects and libraries. I have been able to contribute, publish jakarta > compatible versions and get releases for some of them (Jakarta EE APIs Uber > jar, Geronimo Connectors and Transaction Manager, Geronimo Config, Health, > Metrics, OpenTracing, OpenAPI. OpenJPA, BVal, and OpenWebBeans will be > released soon. > > The big parts is CXF, and ActiveMQ. I had to get them done in TomEE and > update all group/artifact ids. It's under deps, alongside with SXC, DBCP, > and others. > > In terms of removal, I tried to remove old stuff like SAAJ Axis 1 > integration, JAX RPC, Management J2EE and a couple of other old things. > > A lot of other libraries got updated to their latest version when > available in the new jakarta namespace. > > I'm starting to get all the build stable and many modules are passing now, > including all CXF webservices, OpenEJB Core, and others. I can get a build > and run TomEE. > > Goal is to get a green build asap so we can start working on TCK. > The "quick" build is now green. Working on the full build. > > I'll soon be creating a branch for TomEE 8.x maintenance and merge the PR. > I'm hoping we can then have small PRs or at least more people working in > parallel. > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com >
TomEE 9.x - from javax to jakarta namespace
Hi, I've been working for quite a long time on TomEE 9.x, and it's been more challenging and painful than I was expecting. I thought it would be good to give you some sort of status. I created a PR for the work. As a reminder, since Java EE moved to Eclipse to become Jakarta EE, we had a switch from javax.* namespace to jakarta.* namespace. This is an impacting change, since all applications and applications servers are built on top of it. In TomEE, we decided to do that change in TomEE. We had previously a bytecode change approach like an application could do. It worked and we were able to get certified. But it had a lot of limitations, so we had to do the migration in the code and fix all compatibility issues. Here is the PR https://github.com/apache/tomee/pull/814 It has 90+ commits and nearly 5000 files touched (added, removed, updated). I understand it's a lot and it makes it almost impossible to review. But I did not see much approaches in this scenario to create smaller PRs. I created a Jenkins build though available at https://ci-builds.apache.org/job/Tomee/job/master-build-quick-9.x/ It makes it possible to track the progress. There have been steps forward and steps backward. All the code does not sit under TomEE, we use a bunch of third party projects and libraries. I have been able to contribute, publish jakarta compatible versions and get releases for some of them (Jakarta EE APIs Uber jar, Geronimo Connectors and Transaction Manager, Geronimo Config, Health, Metrics, OpenTracing, OpenAPI. OpenJPA, BVal, and OpenWebBeans will be released soon. The big parts is CXF, and ActiveMQ. I had to get them done in TomEE and update all group/artifact ids. It's under deps, alongside with SXC, DBCP, and others. In terms of removal, I tried to remove old stuff like SAAJ Axis 1 integration, JAX RPC, Management J2EE and a couple of other old things. A lot of other libraries got updated to their latest version when available in the new jakarta namespace. I'm starting to get all the build stable and many modules are passing now, including all CXF webservices, OpenEJB Core, and others. I can get a build and run TomEE. Goal is to get a green build asap so we can start working on TCK. The "quick" build is now green. Working on the full build. I'll soon be creating a branch for TomEE 8.x maintenance and merge the PR. I'm hoping we can then have small PRs or at least more people working in parallel. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com
