On 05.06.2012 16:57, Ralph Goers wrote: > I originally had the Flume Appender packaged with the log4j2 core > module. Then Flume went and created an incompatible version. At that > point it became obvious that it was nuts to package flume with log4j, > much less two versions of Flume. > > Ideally, log4j should have as few dependencies as possible. If a > component requires dependencies most users won't want then I'd vote to > move it to a separate module.
A conclusion which may be perfectly valid for flume does not necessarily apply to javax.mail which does not suffer from API instability. We are talking abut the o.a.log4j.net module which would seem to be rather widely used. BTW, the present discussion on whether to modularize o.a.log4j.net or not should not mask the agreement on the necessity to modularize chainsaw, lf5, nt, performance. and contribs. The latter two could be even zapped. -- Ceki http://twitter.com/#!/ceki --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
