Hello
wt., 5 lip 2022 o 15:23 Eric Lilja <mindcoo...@gmail.com> 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 <gr.grzy...@gmail.com> > 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 > > >
