Short update: I think, that we have now resolved those issues and are good to proceed with a M2. I might find some time to set up a RC this week.
@Mojarra: Thanks to Markus (Jung), who added a workaround for the Mojarra issue. Mojarra itself will fix it in their next release, but for now we are good to go. @CXF: Current main now relies on my CXF fork (which is available via central). CXF will most likely release this year. After M2 has been released, I will revert the commit and switch back to the SNAPSHOT, so we have direct feedback if anything breaks. The forked version does pass most of the JAX-RS TCK tests, so it should be ok for usage inside of M2. Gruß Richard On 2024/07/08 08:43:30 Richard Zowalla wrote: > Hi all, > > We had quite a few fixes and dependency updates since we released M1 (like > Java 17 baseline, ams, cxc, mp updates), see > > https://issues.apache.org/jira/projects/TOMEE/versions/12354473 > > > Currently, we have two open things, we need to discuss > > (1) https://github.com/apache/tomee/pull/1229 > (2) https://issues.apache.org/jira/browse/TOMEE-4355 > > > Regarding > > - (1): Are there any objections (ping @PMC) in temporary integrating my CXF > fork until CXF has a stable release? If I do not hear back on this matter, I > will assume lazy consensus. > - (2): This is a bit more difficult because it boils down to spec / ambiguity > and discussion. See the issue and linked OWB for details. I don’t think it is > a blocker for M2 (as it can be solved by downgrading to Mojarra 4.0.0, which > doesn’t have the changes). I would suggest, that we downgrade Mojarra for a > potential M2 release to avoid surprises until it is resolved either in TomEE, > OWB or Mojarra. > > > Any other thoughts? > > Gruß > Richard
