I thought the problem was that it required Java 7, not 8. None of the pax-logging dependencies require Java 8.
On 6 September 2016 at 09:16, Jean-Baptiste Onofré < jeanbaptiste.ono...@gmail.com> wrote: > We discussed while ago to a Java version change we did on Pax Logging > 1.8.x: this version requires Java8 whereas it was supposed to work with > Java6 as well. > > So, what I propose is to release 1.8.6 asap and prepare the rollback of > Java8 requirement. > > Regards > JB > > > On Tuesday, September 6, 2016 at 3:31:00 PM UTC+2, ra...@evosent.com > wrote: >> >> As far as I can see, releasing 1.8.6 can be really quick – and it's long >> overdue. It's basically releasing the master branch......... >> >> 1.9.0 will be a bit more complicated – as it'll require maven plugin >> upgrades and heavy testing. >> >> I don't think we should tackle both things at the same time. There's not >> even a branch for 1.9.0, and no work done towards it as far as I can see. >> >> If you can make the 1.8.6 release today – it will be greatly appreciated, >> JB! >> >> Thank you. >> >> On Tuesday, 6 September 2016 14:52:51 UTC+2, Jean-Baptiste Onofré wrote: >>> >>> Hi, >>> >>> I'm preparing the branches for the two releases: 1.8.6 and 1.9.0 (due to >>> the Java version change). >>> >>> Regards >>> JB >>> >>> On Tuesday, September 6, 2016 at 2:44:00 PM UTC+2, ra...@evosent.com >>> wrote: >>>> >>>> Hi JB, >>>> >>>> Do we have any instructions in the OPS4j community so I can perform the >>>> release myself? We really need the 1.8.6 release ASAP! >>>> >>>> Thank you. >>>> >>>> On Monday, 20 June 2016 19:10:19 UTC+2, Matt Sicker wrote: >>>>> >>>>> Hey, any updates on this? >>>>> >>>>> On 6 June 2016 at 17:18, Matt Sicker <boa...@gmail.com> wrote: >>>>> >>>>>> Even better! >>>>>> >>>>>> On 6 June 2016 at 16:52, <ra...@evosent.com> wrote: >>>>>> >>>>>>> The OSGi import issues following the Logback 1.1.7 upgrades are now >>>>>>> fixed. So please stick with Logback 1.1.7 for the 1.8.6 release. >>>>>>> >>>>>>> Thanks! >>>>>>> >>>>>>> >>>>>>> On Monday, 6 June 2016 19:41:06 UTC+1, Jean-Baptiste Onofré wrote: >>>>>>>> >>>>>>>> Agree, even if I don't like that much, it makes sense. >>>>>>>> >>>>>>>> Regards >>>>>>>> JB >>>>>>>> >>>>>>>> On Monday, June 6, 2016 at 8:36:51 PM UTC+2, Matt Sicker wrote: >>>>>>>>> >>>>>>>>> So should we stick with Logback 1.1.2 and Log4j 2.3 for the 1.8.x >>>>>>>>> release? That makes the most sense. >>>>>>>>> >>>>>>>>> On 6 June 2016 at 13:31, Jean-Baptiste Onofré < >>>>>>>>> jeanbapti...@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Thanks for the update. I'm busy with Karaf 3.0.7 (and other Karaf >>>>>>>>>> subprojects) release preparation. I will tackle pax-logging just >>>>>>>>>> after. >>>>>>>>>> >>>>>>>>>> Regards >>>>>>>>>> JB >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Monday, June 6, 2016 at 8:29:56 PM UTC+2, ra...@evosent.com >>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> Hi guys, >>>>>>>>>>> >>>>>>>>>>> Well, it turns out that the upgrade from Logback 1.1.2 => 1.1.7 >>>>>>>>>>> was not as easy as I expected. In between, the developers at Logback >>>>>>>>>>> introduced dependencies on these additional packages: >>>>>>>>>>> org.slf4j.event, org.codehaus.groovy.transform. >>>>>>>>>>> Obviously the Groovy one can be marked as optional; I'm checking the >>>>>>>>>>> upstream source to understand when and how o.slf4j.event is used. >>>>>>>>>>> >>>>>>>>>>> Cheers. >>>>>>>>>>> >>>>>>>>>>> On Thursday, 2 June 2016 15:14:26 UTC+1, Matt Sicker wrote: >>>>>>>>>>>> >>>>>>>>>>>> I'd prefer to downgrade to 2.3 in 1.8.6, then by the time we >>>>>>>>>>>> get 1.9.0, log4j 2.6.1 should be released. >>>>>>>>>>>> >>>>>>>>>>>> On 2 June 2016 at 08:46, Jean-Baptiste Onofré < >>>>>>>>>>>> jeanbapti...@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Basically, we want to avoid to break backward compability on >>>>>>>>>>>>> minor version. It's unfortunately what we did in 1.8.6. >>>>>>>>>>>>> So, we have to: >>>>>>>>>>>>> 1. Or downgrade to log4j 2.3 to still support Java 6 >>>>>>>>>>>>> 2. Or remove log4j 2 support in pax-logging 1.8.x, and create >>>>>>>>>>>>> new major branch 1.9 with log4j 2 support. >>>>>>>>>>>>> >>>>>>>>>>>>> Regards >>>>>>>>>>>>> JB >>>>>>>>>>>>> >>>>>>>>>>>>> On Thursday, June 2, 2016 at 3:43:05 PM UTC+2, Matt Sicker >>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Wait, do you want Java 6 or 7 compatibility in 1.8.6? If it's >>>>>>>>>>>>>> 6, we can downgrade log4j to 2.3. If it's 7, then it can be the >>>>>>>>>>>>>> latest >>>>>>>>>>>>>> version. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On 1 June 2016 at 23:12, Jean-Baptiste Onofré < >>>>>>>>>>>>>> jeanbapti...@gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> The purpose is: >>>>>>>>>>>>>>> - remove log4j2 support in pax-logging 1.8.6 and go back to >>>>>>>>>>>>>>> Java7 compatibility >>>>>>>>>>>>>>> - release pax-logging 1.9.0 with log4j2 and Java8 only >>>>>>>>>>>>>>> compliant >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Regards >>>>>>>>>>>>>>> JB >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wednesday, June 1, 2016 at 8:28:40 PM UTC+2, Matt Sicker >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Same for upgrading log4j to 2.6. Should get it all done in >>>>>>>>>>>>>>>> a single release. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On 1 June 2016 at 12:08, Jean-Baptiste Onofré < >>>>>>>>>>>>>>>> jeanbapti...@gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> yes, it's on my TODO for next week. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Regards >>>>>>>>>>>>>>>>> JB >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Wednesday, June 1, 2016 at 7:00:30 PM UTC+2, >>>>>>>>>>>>>>>>> ra...@evosent.com wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hey awesome people, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I just upgraded Logback from 1.1.2 to 1.1.7 in master. >>>>>>>>>>>>>>>>>> Would it be possible to make a release of pax-logging 1.8.6? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>>>>> Raúl. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> ------------------ >>>>>>>>>>>>>>>>> OPS4J - http://www.ops4j.org - op...@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+un...@googlegroups.com. >>>>>>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout >>>>>>>>>>>>>>>>> . >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Matt Sicker <boa...@gmail.com> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> ------------------ >>>>>>>>>>>>>>> OPS4J - http://www.ops4j.org - op...@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+un...@googlegroups.com. >>>>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Matt Sicker <boa...@gmail.com> >>>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> -- >>>>>>>>>>>>> ------------------ >>>>>>>>>>>>> OPS4J - http://www.ops4j.org - op...@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+un...@googlegroups.com. >>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Matt Sicker <boa...@gmail.com> >>>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>> -- >>>>>>>>>> ------------------ >>>>>>>>>> OPS4J - http://www.ops4j.org - op...@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+un...@googlegroups.com. >>>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Matt Sicker <boa...@gmail.com> >>>>>>>>> >>>>>>>> -- >>>>>>> -- >>>>>>> ------------------ >>>>>>> OPS4J - http://www.ops4j.org - op...@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+un...@googlegroups.com. >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Matt Sicker <boa...@gmail.com> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Matt Sicker <boa...@gmail.com> >>>>> >>>> -- > -- > ------------------ > 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. > -- Matt Sicker <boa...@gmail.com> -- -- ------------------ 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.
