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.2, but uses xbean-asm5-shaded.
Openwebbeans 2.x uses xbean-asm6-shaded BUT it's CDI 2.0 implementation...

I don't have good solution here. pax-web 6.x already uses asm6 which seems
to be backward (down to JDK8) compatible... I don't think dropping
Openwebbeans 1.x support in pax-cdi 1.0.0 is good idea...

regards
Grzegorz Grzybek

2018-02-01 8:16 GMT+01:00 Grzegorz Grzybek <[email protected]>:

> 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é <[email protected]>:
>
>> 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 (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 we should have Karaf 4.2 using pax-web
>> 7.0.0
>> > due to this OSGi R7 stuff.
>> >
>> > Also, pax-web 6 already uses ASM6, so it should be (probably) Java9
>> ready.
>> >
>> > regards
>> > Grzegorz
>> >
>> > 2018-02-01 7:57 GMT+01:00 Andrea Cosentino <[email protected]>:
>> >
>> >> 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: [email protected]
>> >> Twitter: @oscerd2
>> >> Github: oscerd
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> On Thursday, February 1, 2018, 7:53:49 AM GMT+1, Grzegorz Grzybek <
>> >> [email protected]> wrote:
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> 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-cdi.
>> >>
>> >> I know pax-cdi is not that popular, but still - having 1.0.0.RCx for ~5
>> >> years now isn't nice ;)
>> >>
>> >> As for pax-web 6.1.x upgrade to Jetty 9.4 - I'm OK, as (after I think
>> I've
>> >> collected the right information here
>> >> <https://docs.google.com/spreadsheets/d/1TB_q5r9i8DOIHmBQa1_
>> >> RjsrcjWCwCwsLPj3Pc6FoTJ8/edit#gid=1455909167>
>> >> - see both sheets) Jetty 9.4.x is still Servlets 3.1/JavaEE 7.
>> >>
>> >> best regards
>> >> Grzegorz Grzybek
>> >>
>> >> 2018-01-31 20:59 GMT+01:00 Jean-Baptiste Onofré <[email protected]>:
>> >>
>> >>> 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.
>> >>>
>> >>> Regarding "container", before 4.2.0 release (still planned in couple
>> of
>> >>> weeks), I would like to prepare a 4.1.5 release pretty soon (probably
>> for
>> >>> the weekend). We did good fixes and improvements valuable for users,
>> so
>> >> it
>> >>> makes sense to cut a release.
>> >>>
>> >>> Regards
>> >>> JB
>> >>>
>> >>>
>> >>> On 24/01/2018 15:38, Jean-Baptiste Onofré wrote:
>> >>>
>> >>>> Hi guys,
>> >>>>
>> >>>> Just a quick update about the coming releases.
>> >>>>
>> >>>> 1. Apache Karaf Decanter 2.0.0
>> >>>> I'm working right now on the Decanter 2.0.0 release. It's a major new
>> >>>> releases
>> >>>> (from the new Decanter 2.x series). We are on the right track for
>> this
>> >>>> release,
>> >>>> I should be able to submit to vote during the weekend.
>> >>>>
>> >>>> 2. Karaf Cellar 4.0.4/4.1.2
>> >>>> Some PRs have been merged and I'm reviewing a larger PR. I also have
>> >>>> several
>> >>>> fixes and little improvements on the way. I plan to submit releases
>> to
>> >>>> vote in
>> >>>> roughly 2 weeks.
>> >>>>
>> >>>> 3. Karaf "Container" 4.2.0
>> >>>> After 4.2.0.M1 and 4.2.0.M2, I think we are pretty close to 4.2.0
>> >>>> release. We
>> >>>> still have 18 issues to qualify and eventually fix for this release.
>> One
>> >>>> of
>> >>>> important one is that we have to upgrade to Pax Web 6.1.2 that should
>> >>>> upgrade to
>> >>>> Jetty 9.4.6. It's important to be aligned with latest Camel releases.
>> >>>> So, I started the Jira triage and also started the Pax Web Jetty
>> >> ugprade.
>> >>>> I don't have strong dates in mind for now but hopefully, we should be
>> >>>> able to
>> >>>> cut 4.2.0 in roughly 2 weeks.
>> >>>>
>> >>>> Regards
>> >>>> JB
>> >>>>
>> >>>>
>> >>
>> >
>>
>> --
>> Jean-Baptiste Onofré
>> [email protected]
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
>

Reply via email to