Re: [PAX-LOGGING] Log4J2 problem

2019-05-23 Thread Grzegorz Grzybek
pt., 24 maj 2019 o 08:48 Niclas Hedhman napisał(a): > > I have seen that you have done a lot of good work, and the only thing I > can contribute nowadays is history/background and initial conditions/goals. > And I highly appreciate - those who don't know history are doomed to repeat it ;) regar

Re: [PAX-LOGGING] Log4J2 problem

2019-05-23 Thread Niclas Hedhman
I have seen that you have done a lot of good work, and the only thing I can contribute nowadays is history/background and initial conditions/goals. Cheers Niclas On Fri, May 24, 2019 at 12:52 PM Grzegorz Grzybek wrote: > Hello > > Yes - in ideal world, every jar in Maven Central should be OSGi

Re: [PAX-LOGGING] Log4J2 problem

2019-05-23 Thread Grzegorz Grzybek
Hello Yes - in ideal world, every jar in Maven Central should be OSGi bundle and every closure of dependencies should be consistent. Also, everyone forced to use OSGi hates it and switches to beautiful one-line µservices written in go-lang. org.apache.logging.log4j:log4j-api and log4j-core (log4

Re: [PAX-LOGGING] Log4J2 problem

2019-05-23 Thread Niclas Hedhman
Just because someone added a BND descriptor to Maven/Gradle, doesn't mean that the library is OSGi-capable, let alone OSGi-friendly. Please see https://articles.qos.ch/classloader.html for the starting point, and although the article discusses Java EE classloading, the OSGi scenario isn't any bette