Re: [RELEASE] Preparing Karaf Decanter 2.0.0, Karaf Cellar 4.1.2/4.0.4, and Karaf "Container" 4.2.0

2018-01-31 Thread Grzegorz Grzybek
OK, one more thing about pax-web and pax-cdi. I tried upgrading some versions in pax-cdi and while weld / pax-cdi itself doesn't have problems working with ASM6 / xbean-asm6-shaded (as weld uses own proxy generator from JBoss classwriter), there's problem with openwebbeans... 1.x version is CDI 1.

Re: [RELEASE] Preparing Karaf Decanter 2.0.0, Karaf Cellar 4.1.2/4.0.4, and Karaf "Container" 4.2.0

2018-01-31 Thread Grzegorz Grzybek
Good idea. pax-web 7 won't differ much from 6.1, but it's ok. regards Grzegorz Grzybek 2018-02-01 8:04 GMT+01:00 Jean-Baptiste Onofré : > My concern is more about the Jetty 9.4 update. > > In that case, I would propose: > > 1. Bump master to Pax Web 8.0.x > 2. Create a branch Pax Web 7.0.x based

Re: [RELEASE] Preparing Karaf Decanter 2.0.0, Karaf Cellar 4.1.2/4.0.4, and Karaf "Container" 4.2.0

2018-01-31 Thread Jean-Baptiste Onofré
My concern is more about the Jetty 9.4 update. In that case, I would propose: 1. Bump master to Pax Web 8.0.x 2. Create a branch Pax Web 7.0.x based on 6.x 3. Upgrade to Jetty 9.4 in both master and 7.0.x branch. Thoughts ? Regards JB On 02/01/2018 08:01 AM, Grzegorz Grzybek wrote: > pax-web 7

Re: [RELEASE] Preparing Karaf Decanter 2.0.0, Karaf Cellar 4.1.2/4.0.4, and Karaf "Container" 4.2.0

2018-01-31 Thread Grzegorz Grzybek
pax-web 7 (master branch) is now using jetty 9.3.21.v20170918. Actually I'm not trying to tie pax-web releases to JavaEE releases. I see that master branch (7.0.0-SNAPSHOT) now uses some OSGi R7 JAX-RS samples/whiteboard and I don't think it's production-ready yet. In other words - I don't think

Re: [RELEASE] Preparing Karaf Decanter 2.0.0, Karaf Cellar 4.1.2/4.0.4, and Karaf "Container" 4.2.0

2018-01-31 Thread Jean-Baptiste Onofré
Yes, agree. Upgrading to Jetty 9.4.x means Pax Web 7, especially with Java9 coming. I already updated Jira at OPS4J, and I plan to work on this update today and tomorrow. Regards JB On 02/01/2018 07:57 AM, Andrea Cosentino wrote: > Wasn't Pax-web 7 the version with Jetty 9.4.x support? > > --

Re: [RELEASE] Preparing Karaf Decanter 2.0.0, Karaf Cellar 4.1.2/4.0.4, and Karaf "Container" 4.2.0

2018-01-31 Thread Andrea Cosentino
Wasn't Pax-web 7 the version with Jetty 9.4.x support? -- Andrea Cosentino  -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, February 1, 2018, 7:53:49 AM G

Re: [RELEASE] Preparing Karaf Decanter 2.0.0, Karaf Cellar 4.1.2/4.0.4, and Karaf "Container" 4.2.0

2018-01-31 Thread Jean-Baptiste Onofré
Hi Grzegorz I plan to start a Pax Web 7.0.x branch (upgrade master) for the Jetty 9.4 update. Especially Jetty 9.4 brings Java9 support. We usually bump Pax Web version when upgrading Jetty version. Thoughts ? Regards JB On 02/01/2018 07:53 AM, Grzegorz Grzybek wrote: > Hello > > On PAX-WEB si

Re: [RELEASE] Preparing Karaf Decanter 2.0.0, Karaf Cellar 4.1.2/4.0.4, and Karaf "Container" 4.2.0

2018-01-31 Thread Grzegorz Grzybek
Hello On PAX-WEB side (and wrt PAX-CDI), I did some important, but norrow-scoped changes related to pax-cdi integration. Generally pax-web-jetty now allows to run JSF/CDI WARs without problems (at least MyFaces + Weld). There was minor change needed in pax-web itself and a bit bigger change in pax

Re: [RELEASE] Preparing Karaf Decanter 2.0.0, Karaf Cellar 4.1.2/4.0.4, and Karaf "Container" 4.2.0

2018-01-31 Thread Jean-Baptiste Onofré
Hi, a quick update on the release schedule. As you probably saw, I canceled the Decanter 2.0.0 vote today. I will fix the two pending issues: I should be able to submit a new 2.0.0 release to vote tomorrow. For Cellar releases, I need more time as some changes are wider than expected. Reg

[CANCEL][VOTE] Apache Karaf Decanter 2.0.0 release

2018-01-31 Thread Jean-Baptiste Onofré
Hi guys, unfortunately, I found an annoying issue on Decanter today: https://issues.apache.org/jira/browse/KARAF-5587 It's not new, but it can have an impact for users. As the fix is pretty simple, I prefer to cancel this release to submit a new one including fix in most of appenders. I will s