Hi Guillaume, Hi guys, I tried to register in Jira with no success, so I'm writing here.
When I modified MDCSiftingAppender.java I cloned the repository and worked with my local in github. Since the result was not satisfactory I deleted my local repository, and cloned pax-logging again. But unfortunately then I committed all the changes in the official repo. There was no issue in Jira, there was no mail to general list, so the right thing to do was to revert them till I create the issue (I can't because of the jira problem). So, in latest 1.6.2 MDCSiftingAppender is not modified and PAXLOGGING-100 should be reopened, changes - reviewed and re-applied. Regards, Lazarin On Tue, Apr 26, 2011 at 9:03 AM, Guillaume Nodet (JIRA) <[email protected]> wrote: > Fix MDCSiftingAppender so that old appenders are removed from the internal map > ------------------------------------------------------------------------------ > > Key: PAXLOGGING-100 > URL: http://issues.ops4j.org/browse/PAXLOGGING-100 > Project: Pax Logging > Issue Type: Bug > Components: Service > Reporter: Guillaume Nodet > Fix For: 1.6.2 > > > > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://issues.ops4j.org/secure/Administrators.jspa > - > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
