I have a feeling that PAXLOGGING-132 is also part of this release. I have checked in the code a while back but was uncertain about the procedures for changing the status. It is therefore still set to "unresolved". I guess I should have done this - sorry about that.
Shall I set it to resolved now? /Bengt 2012/2/24 Guillaume Nodet <gno...@gmail.com> > The PaxLogging Team is pleased to announce the availability of a new > bug fix release for the OPS4J PaxLogging framework! > > The 1.6.5 release of pax-logging contains a few bug fixes and > dependency upgrades, including an upgrade to slf4j api 1.6.4 > > For the full changelog head your browser to > http://team.ops4j.org/secure/ReleaseNote.jspa?projectId=10021&version=11388 > . > > -Enjoy > > The PaxLogging Team > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general >
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
