Re: Release heads-up

These all relate to: extension class org.apache.tomee.security.cdi.TomEESecurityExtension not registered, which relates to the new security module. I'll remove that for the release, and then put it straight back to continue work. Jon On Wed, Jul 22, 2020 at 11:24 AM Jonathan Gallimore < jonathan.

Re: Release heads-up

I currently have a handful of JAX-RS failures in the Arquillian test suite: [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.437 s <<< FAILURE! - in org.apache.openejb.arquillian.tests.jaxrs.apppath.AnnotatedApplicationTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Ski

Re: Release heads-up

Ok, can you reopen TOMEE-2809 and target it for 8.0.5? Once this issue is done I can open another one to update to 2.0.17 (which will also require an update to xbean 4.17 and asm8). I think it will be better to do it in 2 steps. On Tue, Jul 21,

Re: Release heads-up

There's definitely an issue. I'll try and dig up some test failure details for you. Thanks for the info below! Jon On Tue, Jul 21, 2020 at 4:58 PM Vicente Rossello wrote: > I tried a few tests in tomee and they worked, and I realized it's something > with a custom CDI extension in my project, s

Re: Release heads-up

I tried a few tests in tomee and they worked, and I realized it's something with a custom CDI extension in my project, so I opened a ticket in openwebbeans: https://issues.apache.org/jira/browse/OWB-1340 I don't know if it's the same case as in tomee project since I'm unable to reproduce it in to

Re: Release heads-up

That's so awesome Vicente, thank you! On Tue, Jul 21, 2020 at 2:30 PM Vicente Rossello wrote: > Of course. I will create a JIRA and investigate it further to see if it can > make 8.0.5 release > > On Tue, Jul 21, 2020 at 3:24 PM Jonathan Gallimore < > jonathan.gallim...@gmail.com> wrote: > > > T

Re: Release heads-up

Of course. I will create a JIRA and investigate it further to see if it can make 8.0.5 release On Tue, Jul 21, 2020 at 3:24 PM Jonathan Gallimore < jonathan.gallim...@gmail.com> wrote: > The JIRA shouldn't be resolved. The update was backed out because it broke > a number of unit tests. > > I'm v

Re: Release heads-up

The JIRA shouldn't be resolved. The update was backed out because it broke a number of unit tests. I'm very happy for you to create a JIRA and work on it, that's much appreciated. I too don't know specifically what the issue is - if you've managed to pin the breakage down to a specific OWB commit,

Re: Release heads-up

Hi, Looking at the OWB upgrade, I see that the JIRA issue is resolved ( https://issues.apache.org/jira/browse/TOMEE-2809 ) but it was reverted in a subsequent commit for some reason (I guess there is an issue with application composer), so 2.0.12 it's still in. I would love to help with this but

Release heads-up

We've had some updated dependencies, some fixes around MDB instance limits, and a couple of other bugs fixes. We're also starting to get into a slight better momentum with regular releases. So - I'm going to roll an 8.0.4 and 9.0.0-M2 release now, and I'll follow up with releases for the two 7.x b

Java EE API jar release heads up

Hi All, I've fixed the TomEE 8, 7.1.x and 7.0.x builds, which has required updating the Java EE API jar that we include with TomEE to pick up an update from Tomcat EL - specifically javax.el.ExpressionFactory#getClassNameServices was returning the first line of the ASF license header as opposed to