Re: Pull request builds

> On Oct 10, 2022, at 12:50 PM, Zowalla, Richard > wrote: > > Hi, > > The INFRA docs [1] do not mention any constraint that the PR needs to > come from the same repository. > > It is also a problem, that we need to rely on different versions of > Java based on a given branch, i.e. Java 8 for

[GitHub] [tomee] rzo1 merged pull request #942: TOMEE-4057 - Remove CXF patch sources with no TomEE-related modifications

rzo1 merged PR #942: URL: https://github.com/apache/tomee/pull/942 -- 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-unsubscr...@tomee.apache.org For

Re: Pull request builds

Hi, The INFRA docs [1] do not mention any constraint that the PR needs to come from the same repository. It is also a problem, that we need to rely on different versions of Java based on a given branch, i.e. Java 8 for 8.x and Java 11 for 9.x, etc - there is no easy way to decide which one to us

Re: [DISCUSS] TomEE 8.0.13 - How do we want to deal with pending CVEs / patch versions?

> Not only it is ridiculous to have two JSON processing stacks cohexisting in TomEE, but also, looking at https://mvnrepository.com/artifact/org.apache.johnzon/johnzon-core, there was no CVE on Johnzon for the part 5 years ; versus a huge number of CVE on Jackson for the same period: https://mvnre

Pull request builds

Was putting some thoughts into how we can maybe keep the build more stable. One obstacle seems to be that the PR builder doesn't build PRs unless they're coming from branches inside the apache/tomee.git repo, not branches from a fork. Is anyone else seeing the same thing or have any information

Remaining test failures

I've been working on the test failures in the main build. We're down to about 7 from our usual 14-17. This test doesn't fail for me. Is anyone else able to reproduce it? - MDBWithWildcardTest I found the commit this started failing in through a git bisect. - FullPoolFailoverTest.testConnec

Re: TomEE Jakarta and CXF

> On Oct 10, 2022, at 8:40 AM, Zowalla, Richard > wrote: > >> One thing we need to start removing for TomEE 10 is all the shading >> operations we do on various libraries, CXF being one of them. They > make >> TomEE development harder and also break dependency management. > > +1 - it is definit

Re: [DISCUSS] TomEE 8.0.13 - How do we want to deal with pending CVEs / patch versions?

Hi all, thanks for your opinions. Regarding (1): Updated to the RC version. Regarding (2): Added the workaround for hsqldb 2.7.0 - we can remove it after 2.7.1 is available. I am currently working on cleaning up the CXF shading for 8.0.13. This will give us the fixes in those classes, which we

Re: TomEE Jakarta and CXF

> One thing we need to start removing for TomEE 10 is all the shading > operations we do on various libraries, CXF being one of them. They make >TomEE development harder and also break dependency management. +1 - it is definitley a pain ;) Am Montag, dem 10.10.2022 um 10:28 +0200 schrieb Jean-Lo

Re: TomEE Jakarta and CXF

Hi, As I mentioned, I started debugging some TCK failures with CXF, but the learning curve and the JAX-RS specification and CXF stack is a big of a challenge. So I also tried master because it moved to jakarta, but I have the same feedback and concerns that you mentioned David. I don't think it's

Re: [DISCUSS] TomEE 8.0.13 - How do we want to deal with pending CVEs / patch versions?

I'm not much focused on 8.x at the moment. Shipping with a Jackson RC is fine in my opinion. And yes it's ridiculous to have 2 JSON-B/P implementations. The thing is that OpenAPI has a hard dependency on Jackson as opposed to be using standard APIs where you can use any implementation. -- Jean-

Re: [DISCUSS] TomEE 8.0.13 - How do we want to deal with pending CVEs / patch versions?

Hi all, I agree with Alex’s comments on Richard’s proposed options for the next TomEE 8.x release. We should move on and ship 8.0.13 soon. Best Martin — https://twitter.com/mawiesne > Am 09.10.2022 um 13:11 schrieb Alex The Rocker : > > Hello, > > Regarding #