Hello

OK - I'll send ops4j announcement soon, but tl;dr version here.

I've released:
 - pax-transx 0.4.2
 - pax-jms 1.0.3
 - pax-jdbc 1.3.2
 - pax-cdi 1.1.0
 - pax-web 7.2.7

All releases use same versions of some important bundles (e.g., xbean
4.12). pax-cdi is upgraded to latest weld2 and owb1.

Also check http://people.apache.org/~ggrzybek/bundle-report-full-karaf.xml
report - it's perfectly aligned, not including hibernate features (which we
use directly from upstream hibernate projects) - but nothing that can't be
tweaked using etc/org.apache.karaf.features.xml.

I'm doing last tests with KARAF-6074 "Race condition between the
FeaturesService and FeatureDeploymentListener" and my work is done here.

@Benjamin Graf - I remember about your suggestion for consistency report,
but I wasn't able to check it this week - it was very busy week for me.

best regards
Grzegorz Grzybek

wt., 15 sty 2019 o 18:35 Grzegorz Grzybek <[email protected]> napisał(a):

> Hello
>
> Looks like it's going to be kind of "release train" :)
>
> I've prepared local versions of:
>  - pax-transx
>  - pax-jms
>  - pax-jdbc
>  - pax-cdi
>  - pax-web
>  - karaf itself
>
> I aligned the differences, so there's now 24 "duplicates" instead of 47.
> Out of these 21, 17 are spring duplicates (simply because Karaf uses 5.0
> and 5.1). and remaining ones are quite irrelevant (JPA 2.1 + 2.2 for
> example in openjpa and openjpa3 features).
>
> I could successfully use xbean 4.12 across pax-cdi, pax-web and karaf
> (using xbean-asm7-shaded) - all pax-cdi and pax-web tests pass.
> commons-codec 1.11 is included (single version of this library across all
> the above projects)
>
> about pax-cdi - that's interesting - I could successfully clear some
> problems, use latest weld and openwebbeans (CDI 1.2) and use xbean 4.12
>
> Tomorrow I'm going to release all 5 above pax-* projects.
>
> best regards
> Grzegorz Grzybek
>
> pon., 14 sty 2019 o 15:52 Grzegorz Grzybek <[email protected]>
> napisał(a):
>
>> Hello
>>
>> So far so good. I used single xbean in pax-cdi 1.0.1-SNAPSHOT (probably
>> I'll end up with 1.1.0-SNAPSHOT) - xbean 4.12 (with xbean-asm7-shaded).
>>
>> Karaf tests work fine and we can have single set of xbean-* artifacts.
>>
>> regards
>> Grzegorz Grzybek
>>
>> pon., 14 sty 2019 o 13:44 Jean-Baptiste Onofré <[email protected]>
>> napisał(a):
>>
>>> OK, go for xbean and commons-codec.
>>>
>>> Thanks,
>>> Regards
>>> JB
>>>
>>> On 14/01/2019 13:38, Grzegorz Grzybek wrote:
>>> > Thanks for reporting alignment problems
>>> >
>>> > Here's the report:
>>> > http://people.apache.org/~ggrzybek/bundle-report-full-karaf.xml (see
>>> my
>>> > previous emails about how to generate it[1]).
>>> >
>>> > Somehow pax-web 7.2.6 can't get into Maven Central. But as you pointed
>>> out,
>>> > I think it's worth doing next pax-cdi release too (version alignment
>>> only).
>>> >
>>> > JB - please leave xbean and commons-codec to me - I'll have them
>>> aligned ok?
>>> >
>>> > regards
>>> > Grzegorz Grzybek
>>> > ===
>>> > [1]:
>>> >
>>> http://karaf.922171.n3.nabble.com/Version-alignment-report-for-Karaf-4-2-3-SNAPSHOT-1-2-td4054786.html
>>> >
>>> >
>>> >
>>> > pon., 14 sty 2019 o 13:34 Jean-Baptiste Onofré <[email protected]>
>>> napisał(a):
>>> >
>>> >> Hi Robert,
>>> >>
>>> >> already done on a local branch. I'm creating the corresponding Jira.
>>> >>
>>> >> Thanks,
>>> >> Regards
>>> >> JB
>>> >>
>>> >> On 14/01/2019 13:26, Robert Varga wrote:
>>> >>> On 14/01/2019 13:14, Jean-Baptiste Onofré wrote:
>>> >>>> Good point.
>>> >>>>
>>> >>>> Greg or I will tackle this.
>>> >>>
>>> >>>
>>> >>> Hello guys,
>>> >>>
>>> >>> while you are looking at this, would it make sense to align
>>> >>> commons-codec at upgraded 1.11 release?
>>> >>>
>>> >>> Thanks,
>>> >>> Robert
>>> >>>
>>> >>
>>> >> --
>>> >> Jean-Baptiste Onofré
>>> >> [email protected]
>>> >> http://blog.nanthrax.net
>>> >> Talend - http://www.talend.com
>>> >>
>>> >
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> [email protected]
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>

Reply via email to