reta commented on PR #912: URL: https://github.com/apache/cxf/pull/912#issuecomment-1123932696
> > > @reta I meant when can we merge the CXF-8371 to master . And we probably need plan some Alpha or Milestone release in the jakarta 4.x CXF and make CI work , then we don 't need to maintain the CXF-8371 branch anymore. > > > > > > @jimma I don't have any objections, ideally it would be great to megre when at least major issues (listed in description) are addressed but it could take a while. But realistically, once JMS (migration to Artemis) is ready, nothing is pending for this branch and we could get it to master. @coheigea @ffang what do you think guys? > > CI is actually running on every commit [1] > > [1] https://ci-builds.apache.org/job/CXF/job/pipeline/job/CXF-8371 > > @reta Good to know this is already works. Is it better to add the "-fae" flag to see all the test failures ? Done, https://ci-builds.apache.org/job/CXF/job/pipeline/job/CXF-8371/38/consoleFull > I wrongly saw this CI result : https://ci-builds.apache.org/job/CXF/job/CXF-JDK11-PR/109/, it's still using JDK11 to run. It's good to fix this too. WDYT ? This is the right place since this is a PR build (but we also build `origin` branch pipelines). The thing is, this is our main Jenkins check for `master` - basically where we have all pull requests coming. For `javax.*` we will stay on JDK-11 baseline (as we discussed [1]) so it is probably makes sense to keep it that way. But ... for Jakarta branch (4.0.0) we would need it to use JDK-17 and to be fair, I have not succeeded yet to configure separate pull request builders for different branches. I mean, I could create Jenkins jobs for different branch specs but only one of the jobs triggers. Will be looking into that shortly. [1] https://www.mail-archive.com/dev@cxf.apache.org/msg17023.html -- 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...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
