rzo1 merged pull request #833:
URL: https://github.com/apache/tomee/pull/833
--
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:
github-actions[bot] opened a new pull request #833:
URL: https://github.com/apache/tomee/pull/833
Found some uncommited changes (from BOM regeneration) after running build on
TomEE master
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
This is very close. The dangers of A are not quite captured. Completely agree
with the dangers of B.
> On Apr 1, 2022, at 1:13 AM, Zowalla, Richard
> wrote:
>
> So we basically have to options (if I understand the discussion
> correctly):
>
> (A) Put some effort / resources into upgrade
So we basically have to options (if I understand the discussion
correctly):
(A) Put some effort / resources into upgrade our MP impls to the latest
versions to fully support Jakarta namespace. From my understanding
maintaining these impls is a bit PITA as MP tends to break its API
every few
I agree with both of you :)
It is a common question and is often asked on Stackoverflow: which
version of TomEE supports which JDK, which JEE Standard is covered with
which TomEE version, which TomEE version should be used in 2022, ...
I am sure we can be more clear on the website. I am happy to
The risk for TomEE (IMHO indeed) is that, using smallrye, you break the
core value "apache" or at least "owned by apache" and break the other core
value "lightweight" since it comes with a tons of uneeded stuff and
implementation is not even JAXRS friendly (it breaks literally jaxrs and
cdi at
