Re: logging-log4j2 git commit: [LOG4J2-1976] Update org.osgi.core from 4.3.1 to 6.0.0.

2017-07-10 Thread Matt Sicker
I don't think we have any tests for that. Karaf uses pax-logging-log4j2 which shades in log4j-api and log4j-core together for some reason. I've made some commits on that project before, though I'm not sure why everything is shaded. On 10 July 2017 at 16:53, Gary Gregory wrote: > Even version 6 i

Re: logging-log4j2 git commit: [LOG4J2-1976] Update org.osgi.core from 4.3.1 to 6.0.0.

2017-07-10 Thread Gary Gregory
Even version 6 is three years old... the one we had in there was over 10 IIRC G On Jul 10, 2017 14:42, "Matt Sicker" wrote: > Now I'll admit that I'm not using OSGi anymore nowadays (different client, > different requirements, right?), so I'm not sure on what a reasonable > baseline requirement

Re: logging-log4j2 git commit: [LOG4J2-1976] Update org.osgi.core from 4.3.1 to 6.0.0.

2017-07-10 Thread Gary Gregory
WRT Karaf, do we even have tests for that? G On Jul 10, 2017 14:42, "Matt Sicker" wrote: > Now I'll admit that I'm not using OSGi anymore nowadays (different client, > different requirements, right?), so I'm not sure on what a reasonable > baseline requirement is for the OSGi API. This should b

Re: logging-log4j2 git commit: [LOG4J2-1976] Update org.osgi.core from 4.3.1 to 6.0.0.

2017-07-10 Thread Matt Sicker
Now I'll admit that I'm not using OSGi anymore nowadays (different client, different requirements, right?), so I'm not sure on what a reasonable baseline requirement is for the OSGi API. This should be fine, though at worst we might want to drop it down to 5.0.0. I'm thinking it would be reasonable