[GitHub] [tomee-site-generator] dblevins merged pull request #35: TOMEE-3846 fixed tomee flavors comparison page
dblevins merged pull request #35: URL: https://github.com/apache/tomee-site-generator/pull/35 -- 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
[GitHub] [tomee] rzo1 commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
rzo1 commented on pull request #828: URL: https://github.com/apache/tomee/pull/828#issuecomment-1079700475 I think it is good to have this discussion to clarify what the intended distributions should look like in 2022 considering the history of Plus / Plume and the incosistent current status of the distros / website. So thanks for the additional thoughts @rmannibucau and @sultan -- 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
[GitHub] [tomee] sultan commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
sultan commented on pull request #828: URL: https://github.com/apache/tomee/pull/828#issuecomment-1079668481 webpro and plus have a clear focus to me as well, even though "Plus" branding could be changed to better tell its "Full EE" 🤔 or i can just describe that in the flavors page. You could drop Plume but you would lose the benefits from its "ready to try out" capabilities. i am thinking about the AutoConfiguration for Jakarta Persistence (JPA) which facilitates learning Tomee. -- 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
[GitHub] [tomee] github-actions[bot] closed pull request #829: Regenerated BOMs after dependency upgrades
github-actions[bot] closed pull request #829: URL: https://github.com/apache/tomee/pull/829 -- 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
[GitHub] [tomee] rmannibucau commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
rmannibucau commented on pull request #828: URL: https://github.com/apache/tomee/pull/828#issuecomment-1079662861 Yep, think they shouldnt but as Im not a big user of that I dont care much of what it becomes while webpro and plus stays aligned on their goal ;) -- 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
[GitHub] [tomee] sultan edited a comment on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
sultan edited a comment on pull request #828: URL: https://github.com/apache/tomee/pull/828#issuecomment-1079656491 > AFAIK plume is a webprofile based distro if this is correct then i believe Plume should not contain jars for MicroProfile nor JMS ActiveMQ. but maybe i missed something. about having two different Plume distros, is this something users would really need ?   i am just a contributor but i understood plume is currently leaning towards full EE. not meaning that it must be this way nor that its the devs plan. what do we do ? plan a : continue with the PR to have Plume complete its fall towards the the full ee side. plan b : change it so that Plume loses its MicroProfile and ActiveMQ capabilities. plan c : no changes on distros but with some details on the web page to clarify what is intended. plan d : totally other solution -- 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
[GitHub] [tomee] sultan edited a comment on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
sultan edited a comment on pull request #828: URL: https://github.com/apache/tomee/pull/828#issuecomment-1079656491 > AFAIK plume is a webprofile based distro if this is correct then i believe Plume should not contain jars for MicroProfile nor JMS ActiveMQ. but maybe i missed something. about having two different Plume distros, is this something users would need ?   i am just a contributor but i understood plume is currently leaning towards full EE. not meaning that it must be this way nor that its the devs plan. what do we do ? plan a : continue with the PR to have Plume complete its fall towards the the full ee side. plan b : change it so that Plume loses its MicroProfile and ActiveMQ capabilities. plan c : no changes on distros but with some details on the web page to clarify what is intended. plan d : totally other solution -- 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
[GitHub] [tomee] sultan commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
sultan commented on pull request #828: URL: https://github.com/apache/tomee/pull/828#issuecomment-1079656491 > AFAIK plume is a webprofile based distro if this is correct then Plume should not contains jars for MicroProfile nor JMS ActiveMQ   -- 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
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 > >> > >
[GitHub] [tomee] rzo1 commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
rzo1 commented on pull request #828: URL: https://github.com/apache/tomee/pull/828#issuecomment-1079646878 > AFAIK plume is a webprofile based distro so batchee and jcs should belong to a new "plume-all" distro probably? This originates from this [list thread](https://lists.apache.org/thread/o6tqmsgmc975ddr028ohtw2r8npmzg0m) and @dblevins comment there, that: "Those distributions are supposed to be the same minus the JPA and JSF providers.". There is also a [blog post](https://www.tomitribe.com/blog/tomee-webprofile-vs-tomee-microprofile-vs-tomee-vs-tomee-plume/) about the differences but I am too new to judge the original thoughts regarding "plume" vs "plus". -- 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
[GitHub] [tomee] rmannibucau commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
rmannibucau commented on pull request #828: URL: https://github.com/apache/tomee/pull/828#issuecomment-1079634038 AFAIK plume is a webprofile based distro so batchee and jcs should belong to a new "plume-all" distro probably? -- 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
