I know I haven't had time to spend on this project lately, but I never finished off LOG4J2-609 <https://issues.apache.org/jira/browse/LOG4J2-609>. If you're itching to release this weekend, then I won't be able to get this done. The solution I'm presenting is a little bit invasive in the "API", but I think the current solution has some real problems. The details are in the JIRA. I only bring it up in case you think this area of the API should not be allowed to change after 2.0. It is kind of off in a corner where most people won't go, so maybe it will be acceptable to fix for a 2.1 release. Where it stands right now, I don't have the tests working, which I now thing is showing a problem with something in my solution.
What are your thoughts? Other than that, I would really like to see 2.0 released. On Fri, Jul 11, 2014 at 8:47 PM, Remko Popma <[email protected]> wrote: > > > On Friday, July 11, 2014, Remko Popma <[email protected]> wrote: > >> No objection at all! >> >> I would like to add the tool to generate Custom/Extended Loggers, and do >> a doc fix for LOG4J2-631. > > Done with these changes. > >> >> Also, the site now has an empty section "Custom Plugins" under manual > >> Extending Log4j. Shall we remove that before the release? > > I haven't had time to do this. I may not have time today either. Perhaps > not that urgent anyway... > > One more thing (gentle reminder): let's not forget to change to the new > logo. :-) > > >> >> Sent from my iPhone >> >> > On 2014/07/11, at 15:50, Ralph Goers <[email protected]> >> wrote: >> > >> > I would like to do the release for Log4j 2.0 this weekend. Are there >> any objections? >> > >> > Ralph >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> > -- Bruce Brouwer about.me/bruce.brouwer [image: Bruce Brouwer on about.me] <http://about.me/bruce.brouwer>
