You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by GitBox <gi...@apache.org> on 2022/03/26 01:47:54 UTC
[GitHub] [tomee] sultan opened a new pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
sultan opened a new pull request #828:
URL: https://github.com/apache/tomee/pull/828
batchee and jcs added in Plume to reflect Plus flavor
removed xml api from from Plume to reflect Plus flavor
remains some jar refs in jar scan exclusions (xerces, xml-apis)
--
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-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tomee] rzo1 commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
Posted by GitBox <gi...@apache.org>.
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-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tomee] rzo1 commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
Posted by GitBox <gi...@apache.org>.
rzo1 commented on pull request #828:
URL: https://github.com/apache/tomee/pull/828#issuecomment-1084151416
@sultan Can you check your rebase with `tomee-8.x`. It does not look sane to me (at least judging from the changeset now).
--
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-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tomee] sultan edited a comment on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
Posted by GitBox <gi...@apache.org>.
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-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tomee] dblevins commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
Posted by GitBox <gi...@apache.org>.
dblevins commented on pull request #828:
URL: https://github.com/apache/tomee/pull/828#issuecomment-1081014317
Here's the list message on the name and motivation for Plume:
- https://lists.apache.org/thread/tkpfjlzv70y8kzz5f905qj9vs95b34rw
"a version of TomEE Plus with Mojarra and EclipseLink. Tentatively called it "TomEE Plume" which stands for TomEE PLUs, Mojarra, Eclipselink (PLU.M.E)."
--
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-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tomee] rmannibucau commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
Posted by GitBox <gi...@apache.org>.
rmannibucau commented on pull request #828:
URL: https://github.com/apache/tomee/pull/828#issuecomment-1081455368
> there could be an external tool to modify a dezipped certified TomEE to change its implementation jars.
If you look tomee-maven-plugin it enables to do any distro from plain tomcat to advanced customized tomee and you can use it to build a tomee plume from tomee webprofile or any distro ;). Installer is legacy since years :)
--
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-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tomee] sultan commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
Posted by GitBox <gi...@apache.org>.
sultan commented on pull request #828:
URL: https://github.com/apache/tomee/pull/828#issuecomment-1084176117
i think i was able to clean up my mess by reverting to my previous draft. commits seems legit now. can someone launch checks ?
--
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-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tomee] rmannibucau commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
Posted by GitBox <gi...@apache.org>.
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-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tomee] sultan commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
Posted by GitBox <gi...@apache.org>.
sultan commented on pull request #828:
URL: https://github.com/apache/tomee/pull/828#issuecomment-1081054794
nice to read !
1) i learned that a setup installer for TomEE "like eclipse oomph" (cherry pick modules) is not possible, as it breaks TCK rules. unless we want a parallel non TCK certified TomEE (meh)
2) i thought like @rmannibucau at first with "per functionalities" LIB folders (like others EE servers) but this would make TomEE harder to configure / extend. (where do user put their jars !?)
3) there could be "per functionalities" uber or shaded jars to ease remove and replace implementations by others. but i wonder if i did read that current project policy is to avoid shading/uber.
4) there could be a common POM between plus and plume to help fill the gaps/ease maintenance.
5) there could be an external tool to modify a dezipped certified TomEE to change its implementation jars.
the only one i think i can currently help on is n°4 (common plus-plume pom)
--
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-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tomee] rmannibucau commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
Posted by GitBox <gi...@apache.org>.
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-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tomee] sultan edited a comment on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
Posted by GitBox <gi...@apache.org>.
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-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tomee] sultan commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
Posted by GitBox <gi...@apache.org>.
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-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tomee] sultan commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
Posted by GitBox <gi...@apache.org>.
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-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tomee] rzo1 commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
Posted by GitBox <gi...@apache.org>.
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-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tomee] sultan commented on pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
Posted by GitBox <gi...@apache.org>.
sultan commented on pull request #828:
URL: https://github.com/apache/tomee/pull/828#issuecomment-1081002793
does this need a mailing list vote from committers ?
--
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-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [tomee] rzo1 merged pull request #828: TOMEE-3871 - TomEE Plume is missing BatchEE / JCS Cache
Posted by GitBox <gi...@apache.org>.
rzo1 merged pull request #828:
URL: https://github.com/apache/tomee/pull/828
--
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-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org