Hello, 1+ for (2) On Mon, Jul 8, 2024, 06:40 Thomas Andraschko <andraschko.tho...@gmail.com> wrote:
> +1, like markus suggested > > Am Mo., 8. Juli 2024 um 11:15 Uhr schrieb Markus Jung <ju...@apache.org>: > > > Hey Richard, > > > > > > no strong opinion for (1) from my side, if there are no objections we > > should just merge it so we can push another milestone release IMO. +1 to > > downgrade Mojarra to 4.0.0 to make tomee-plume usable again until we > > figure out where and how to fix Mojarra 4.0.1+ integration with OWB. > > > > > > Generally huge +1 to release M2 > > > > > > Thanks > > > > Markus > > > > On 08.07.24 10:43, 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 > > >
