2012/6/5 Gary Gregory <garydgreg...@gmail.com>: > On Tue, Jun 5, 2012 at 8:45 AM, ceki <c...@qos.ch> wrote: >> >> On 01.06.2012 04:41, Ralph Goers wrote: >>> >>> If you don't do that then you end up with a bunch of optional >>> dependencies that you will forget to include or a bunch of required >>> dependencies that you may not really need. >>> >>> Separating the API from the impl is useful as it keeps users from >>> accessing stuff that wasn't meant to be public - which is one of the >>> more serious problems in 1.x. >>> >>> Ralph >> >> >> Agreed. Separating chainsaw and lf5 into new modules is most >> reasonable. However, modularization can be easily overdone. Assuming >> the code in org.apache.log4j.net has not changed much since the last >> time I looked, I would recommend that the org.apache.log4j.net be part >> of the core module, not separate. > > > +1, please don't over do it. And at least give me an option to use one > server-side jar to rule them all.
As I said before, create another module built with Shade plugin. You can do it, but it is useful only for non Maven users. Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
