Re: Next TomEE+ 7.1.x release
Hi Cesar, Thanks for the info. I have some work deadline this week. I'll look through next week. Thanks. Geeth On Wed, May 4, 2022, 5:01 PM Cesar Hernandez wrote: > Hello, > > > 7.1.x full build is back to green: > > https://ci-builds.apache.org/job/Tomee/job/tomee-7.1.x/11/ > > > @Richard, that's awesome, thank you! > > > Let me start on the workflow items and then look at the dependencies to see > > > Hi, @Geeth, on the top of my head, the following dependencies may need to > be updated.: > >- Tomcat >- cxf >- mojarra >- jackson >- santuario > > The job https://ci-builds.apache.org/job/Tomee/job/pull-request/ listen to > PR's against TomEE 7.1.x branch, among others, so feedback is > automatically provided if you open a PR. > > > > > > > El sáb, 23 abr 2022 a las 13:13, Zowalla, Richard (< > richard.zowa...@hs-heilbronn.de>) escribió: > > > Hi, > > > > did some fixes and now the 7.1.x full build is back to green: > > https://ci-builds.apache.org/job/Tomee/job/tomee-7.1.x/11/ > > > > That means we are in good shape for the dependency updates as we now have > > a valid baseline and any change can be validated via CI. > > > > Gruß > > Richard > > > > Von: Geeth Narayanan > > Gesendet: Freitag, 22. April 2022 14:47:27 > > An: dev@tomee.apache.org > > Betreff: Re: Next TomEE+ 7.1.x release > > > > Thanks, Richard and Jean-Louis. Appreciate your flexibility. > > > > Let me start on the workflow items and then look at the dependencies to > see > > what's included and maybe go out the latest minor version in that > mainline > > version. > > > > Will keep you posted. > > > > On Fri, Apr 22, 2022 at 4:18 AM Jean-Louis Monteiro < > > jlmonte...@tomitribe.com> wrote: > > > > > Hi, > > > > > > Thanks Richard for restoring a CI for the 7.1.x branch. > > > > > > If we can have multiple PRs to update the dependencies and the build is > > > green, I agree with Richard, it should not be a big problem to do the > > > release. > > > > > > -- > > > Jean-Louis Monteiro > > > http://twitter.com/jlouismonteiro > > > http://www.tomitribe.com > > > > > > > > > On Fri, Apr 22, 2022 at 8:02 AM Zowalla, Richard < > > > richard.zowa...@hs-heilbronn.de> wrote: > > > > > > > Hi Geeth, > > > > > > > > thanks for your first contribution to TomEE. It is very much > > > > appreciated. > > > > > > > > The last release was in 2020 and most effort has been shifted to 8.x > > > > and 9.x. Personally, I do not use 7.1.x in any project anymore. > > > > Therefore, I am unable to test related binaries. > > > > > > > > Nevertheless, I appreciate your attitude in offering help in > reviewing > > > > / contributing. Therefore, I created / restored the CI environment > for > > > > 7.1.x [1] and triggered a full build, so we get some information how > > > > the current build looks like. > > > > > > > > With a working CI env in place, we would need to conduct (or at least > > > > try) some dependency updates (like Tomcat, BatchEE (maybe?), CXF > > > > (maybe?), Johnzon (maybe?), OWB (maybe?), ActiveMQ (maybe?), MyFaces > > > > (maybe?), Mojarra (maybe?), Jackson (maybe - used in Microprofile), > > > > etc.) and find the latest corresponding versions supporting EE7. > > > > > > > > Perhaps that would be a good starting point to contribute, if you > have > > > > some spare time / resources available. > > > > > > > > Our basic contribution workflow would be: > > > > > > > > (1) Create a Jira (e.g. for a version update) > > > > (2) Ask on the dev@ list to be assigned > > > > (3) Work on the issue. Ask for help / guidance if needed > > > > (4) Create a PR. > > > > (5) Ask for review on dev@ > > > > > > > > In addition it needs some fixes on the structure of the project > itself > > > > (SCM urls as git-wip-us went EOL a few weeks ago). If we decide to > > > > pursue this further, I can do these (structural) changes. > > > > > > > > If the CI is green afterwards, a potential 7.1.5 would be in a good > > > > shape IMHO. > > > > > > > > The (mechanical) work to conduct a release isn't that much of an > effort > > > > but requires a TomEE PMC member for some of the steps (eg. the vote, > > > > etc.). > > > > > > > > The list of currently resolved issues for a 7.1.5 is here: [2] > > > > > > > > Gruß > > > > Richard > > > > > > > > > > > > [1] https://ci-builds.apache.org/job/Tomee/job/tomee-7.1.x/ > > > > [2] https://issues.apache.org/jira/projects/TOMEE/versions/12349482 > > > > > > > > Am Donnerstag, dem 21.04.2022 um 19:29 -0500 schrieb Geeth Narayanan: > > > > > Hi, > > > > > > > > > > I recently made my first code contribution as a patch to 7.1.x > > > > > release. > > > > > This was for a startup issue that has been fixed in 8.x. It was > also > > > > > not > > > > > present in 7.1.1, but was introduced in 7.1.2. > > > > > > > > > > I understand that the team's focus is to release 8.x and 9.x, but I > > > > > was > > > > > wondering if you could put out 7.1.5 with this change and anything > > > >
Re: Next TomEE+ 7.1.x release
Hello, 7.1.x full build is back to green: > https://ci-builds.apache.org/job/Tomee/job/tomee-7.1.x/11/ @Richard, that's awesome, thank you! Let me start on the workflow items and then look at the dependencies to see Hi, @Geeth, on the top of my head, the following dependencies may need to be updated.: - Tomcat - cxf - mojarra - jackson - santuario The job https://ci-builds.apache.org/job/Tomee/job/pull-request/ listen to PR's against TomEE 7.1.x branch, among others, so feedback is automatically provided if you open a PR. El sáb, 23 abr 2022 a las 13:13, Zowalla, Richard (< richard.zowa...@hs-heilbronn.de>) escribió: > Hi, > > did some fixes and now the 7.1.x full build is back to green: > https://ci-builds.apache.org/job/Tomee/job/tomee-7.1.x/11/ > > That means we are in good shape for the dependency updates as we now have > a valid baseline and any change can be validated via CI. > > Gruß > Richard > > Von: Geeth Narayanan > Gesendet: Freitag, 22. April 2022 14:47:27 > An: dev@tomee.apache.org > Betreff: Re: Next TomEE+ 7.1.x release > > Thanks, Richard and Jean-Louis. Appreciate your flexibility. > > Let me start on the workflow items and then look at the dependencies to see > what's included and maybe go out the latest minor version in that mainline > version. > > Will keep you posted. > > On Fri, Apr 22, 2022 at 4:18 AM Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > > > Hi, > > > > Thanks Richard for restoring a CI for the 7.1.x branch. > > > > If we can have multiple PRs to update the dependencies and the build is > > green, I agree with Richard, it should not be a big problem to do the > > release. > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Fri, Apr 22, 2022 at 8:02 AM Zowalla, Richard < > > richard.zowa...@hs-heilbronn.de> wrote: > > > > > Hi Geeth, > > > > > > thanks for your first contribution to TomEE. It is very much > > > appreciated. > > > > > > The last release was in 2020 and most effort has been shifted to 8.x > > > and 9.x. Personally, I do not use 7.1.x in any project anymore. > > > Therefore, I am unable to test related binaries. > > > > > > Nevertheless, I appreciate your attitude in offering help in reviewing > > > / contributing. Therefore, I created / restored the CI environment for > > > 7.1.x [1] and triggered a full build, so we get some information how > > > the current build looks like. > > > > > > With a working CI env in place, we would need to conduct (or at least > > > try) some dependency updates (like Tomcat, BatchEE (maybe?), CXF > > > (maybe?), Johnzon (maybe?), OWB (maybe?), ActiveMQ (maybe?), MyFaces > > > (maybe?), Mojarra (maybe?), Jackson (maybe - used in Microprofile), > > > etc.) and find the latest corresponding versions supporting EE7. > > > > > > Perhaps that would be a good starting point to contribute, if you have > > > some spare time / resources available. > > > > > > Our basic contribution workflow would be: > > > > > > (1) Create a Jira (e.g. for a version update) > > > (2) Ask on the dev@ list to be assigned > > > (3) Work on the issue. Ask for help / guidance if needed > > > (4) Create a PR. > > > (5) Ask for review on dev@ > > > > > > In addition it needs some fixes on the structure of the project itself > > > (SCM urls as git-wip-us went EOL a few weeks ago). If we decide to > > > pursue this further, I can do these (structural) changes. > > > > > > If the CI is green afterwards, a potential 7.1.5 would be in a good > > > shape IMHO. > > > > > > The (mechanical) work to conduct a release isn't that much of an effort > > > but requires a TomEE PMC member for some of the steps (eg. the vote, > > > etc.). > > > > > > The list of currently resolved issues for a 7.1.5 is here: [2] > > > > > > Gruß > > > Richard > > > > > > > > > [1] https://ci-builds.apache.org/job/Tomee/job/tomee-7.1.x/ > > > [2] https://issues.apache.org/jira/projects/TOMEE/versions/12349482 > > > > > > Am Donnerstag, dem 21.04.2022 um 19:29 -0500 schrieb Geeth Narayanan: > > > > Hi, > > > > > > > > I recently made my first code contribution as a patch to 7.1.x > > > > release. > > > > This was for a startup issue that has been fixed in 8.x. It was also > > > > not > > > > present in 7.1.1, but was introduced in 7.1.2. > > > > > > > > I understand that the team's focus is to release 8.x and 9.x, but I > > > > was > > > > wondering if you could put out 7.1.5 with this change and anything > > > > else in > > > > there. Looks like it's been a while since 7.1.4 was released. > > > > > > > > As I mentioned, it was my first foray into contribution, so please > > > > let me > > > > know if I can help in any way like reviewing binaries or contributing > > > > on > > > > anything else. > > > > > > > > Appreciate the help! > > > > > > > > More information on the issue: > > > > > > > > https://issues.apache.org/jira/browse/TOMEE-2919 > > > >
[GitHub] [tomee] cesarhernandezgt merged pull request #878: TOMEE-3932 added technical document to help on the migration to Jakarta namespace
cesarhernandezgt merged PR #878: URL: https://github.com/apache/tomee/pull/878 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tomee.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
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 >
[GitHub] [tomee] rzo1 commented on pull request #875: TOMEE-3931 fixed cucumber-jvm example and added deps/cucumber-openejb-shade module.
rzo1 commented on PR #875: URL: https://github.com/apache/tomee/pull/875#issuecomment-1116959378 @rmannibucau You are right - I was thinking the same. In the long run, it would be better to have it in cucumber. Therefore, I have opened an issue https://github.com/cucumber/cucumber-jvm/issues/2548, so we can discuss the possible ways of providing a Jakarta artifact at cucumber directly. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tomee.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
