On 2016-09-06 07:48:55 -0700, r...@evosent.com wrote: > Actually, this only affected the pax-logging-log4j2 module, right?
No, all modules. > What prevents these users from running pax-logging-api 1.8.5 with > pax-logging-log4j2 with 1.8.1? > > Our OSGi import version ranges are pretty lax: [0.9.5,2.0.0). The issue was that the compile target was flipped to 1.7 for all modules starting with 1.8.5 thus generating bytecode for JDK7 which of course won't run on JDK6. https://ops4j1.jira.com/browse/PAXLOGGING-210 https://github.com/ops4j/org.ops4j.pax.logging/pull/22 -- -- ------------------ OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
