Re: Optional dependencies are not being resolved on Karaf 4.4.1-SNAPSHOT

[Jean-Baptiste Onofré]

Hi Paul,

do you have a simple test case to reproduce it ?

Regards
JB

On Tue, Jul 5, 2022 at 4:21 PM Paul Stanley  wrote:
>
> Hi JB,
>
> Sorry I've tried a distribution based on 4.4.0, however it keep hitting a new 
> issue with a bundle dead lock on startup.  Rather than investigate that I 
> will go back to looking at what is causing the optional package resolution 
> issue in 4.4.1
> If you have any pointers then please let me know.
>
> Thanks
> Paul
>
> Get TypeApp for Android
> On 2 Jul 2022, at 19:18, "Jean-Baptiste Onofré" 
> mailto:j...@nanthrax.net>> wrote:
>
> Do you observe same behavior on 4.4.0 ?
>
> Le ven. 1 juil. 2022 à 17:23, Paul Stanley  a écrit :
>
>  Hello.
>
>
>  Has anyone else observed optional package resolution issues on karaf
>  4.4.1-SNAPSHOT.
>
>
>  When I build the karaf deployment for my application the majority of the
>  base artifacts get added to the etc/startup.cfg file. These in turn get
>  loaded by the main deployment thread in karaf. At the end of the deployment
>  process these bundles get re-assessed to see if the bundles need to get
>  updated, however this process appears to ignore optional package
>  requirements.
>
>
>  The result is that many of the core services (such as spring-webmvc) fail
>  to functional correctly.  This wasn't an issue in karaf 4.3.  As such,
>  please can the community let me know if this is a general issue that has
>  been seen elsewhere? Or is it something that is peculiar to my setup.
>
>
>  Thanks
>
>  Paul
>
>
>

Re: Optional dependencies are not being resolved on Karaf 4.4.1-SNAPSHOT

[Paul Stanley]

Hi JB,

Sorry I've tried a distribution based on 4.4.0, however it keep hitting a new 
issue with a bundle dead lock on startup.  Rather than investigate that I will 
go back to looking at what is causing the optional package resolution issue in 
4.4.1
If you have any pointers then please let me know.

Thanks
Paul

Get TypeApp for Android
On 2 Jul 2022, at 19:18, "Jean-Baptiste Onofré" 
mailto:j...@nanthrax.net>> wrote:

Do you observe same behavior on 4.4.0 ?

Le ven. 1 juil. 2022 à 17:23, Paul Stanley  a écrit :

 Hello.


 Has anyone else observed optional package resolution issues on karaf
 4.4.1-SNAPSHOT.


 When I build the karaf deployment for my application the majority of the
 base artifacts get added to the etc/startup.cfg file. These in turn get
 loaded by the main deployment thread in karaf. At the end of the deployment
 process these bundles get re-assessed to see if the bundles need to get
 updated, however this process appears to ignore optional package
 requirements.


 The result is that many of the core services (such as spring-webmvc) fail
 to functional correctly.  This wasn't an issue in karaf 4.3.  As such,
 please can the community let me know if this is a general issue that has
 been seen elsewhere? Or is it something that is peculiar to my setup.


 Thanks

 Paul

Re: [ANN] Pax Logging 2.1.3 released

[Grzegorz Grzybek]

Hello


wt., 5 lip 2022 o 15:23 Eric Lilja  napisał(a):

> Great, thanks!
>
> Question: Will Pax Exam be updated to use this version, it uses an ancient
> version doesn't it?
>

I think it does. I never released Pax Exam versions (though I did one
deadlock fix I guess). In all other Pax projects I worked, I used Pax Exam
in "custom mode", which allowed me to use any Pax Logging version I wanted
:) (check Pax Web, Pax JDBC, Pax JMS, Pax Transx).
Pax Logging itself is also tested using Pax Exam ;)

But answering your question, I think there should be no problem upgrading
Pax Exam itself.

regards
Grzegorz Grzybek


>
> - Eric L
>
> On Tue, Jul 5, 2022 at 3:18 PM Grzegorz Grzybek 
> wrote:
>
> > Hello
> >
> > I'd like to announce the release of Pax Logging 2.1.3 with just one
> update:
> >
> >- Log4j2 2.18.0
> >
> > Updating to 2.18.0 helped with one CCE problem related to JeroMqAppender.
> >
> > I'd like to mention that lines 2.0.x and 1.11.x are no longer a priority
> > because they include log4j1 "backend".
> > And line 1.12.x without log4j1 backend is based on OSGi CMPN R6 which is
> > already quite old.
> >
> > So if you can, please migrate to 2.1.x. If you can't, please let us know
> ;)
> >
> > The release notes can be found here:
> >
> >- 2.1.3:
> >https://github.com/ops4j/org.ops4j.pax.logging/milestone/95?closed=1
> >
> > kind regards
> > Grzegorz Grzybek
> >
>

Re: [ANN] Pax Logging 2.1.3 released

[Eric Lilja]

Great, thanks!

Question: Will Pax Exam be updated to use this version, it uses an ancient
version doesn't it?

- Eric L

On Tue, Jul 5, 2022 at 3:18 PM Grzegorz Grzybek 
wrote:

> Hello
>
> I'd like to announce the release of Pax Logging 2.1.3 with just one update:
>
>- Log4j2 2.18.0
>
> Updating to 2.18.0 helped with one CCE problem related to JeroMqAppender.
>
> I'd like to mention that lines 2.0.x and 1.11.x are no longer a priority
> because they include log4j1 "backend".
> And line 1.12.x without log4j1 backend is based on OSGi CMPN R6 which is
> already quite old.
>
> So if you can, please migrate to 2.1.x. If you can't, please let us know ;)
>
> The release notes can be found here:
>
>- 2.1.3:
>https://github.com/ops4j/org.ops4j.pax.logging/milestone/95?closed=1
>
> kind regards
> Grzegorz Grzybek
>

[ANN] Pax Logging 2.1.3 released

[Grzegorz Grzybek]

Hello

I'd like to announce the release of Pax Logging 2.1.3 with just one update:

   - Log4j2 2.18.0

Updating to 2.18.0 helped with one CCE problem related to JeroMqAppender.

I'd like to mention that lines 2.0.x and 1.11.x are no longer a priority
because they include log4j1 "backend".
And line 1.12.x without log4j1 backend is based on OSGi CMPN R6 which is
already quite old.

So if you can, please migrate to 2.1.x. If you can't, please let us know ;)

The release notes can be found here:

   - 2.1.3:
   https://github.com/ops4j/org.ops4j.pax.logging/milestone/95?closed=1

kind regards
Grzegorz Grzybek