Why would that require a 1.3? Ralph
On May 31, 2012, at 2:24 PM, "Jacob Kjome" <h...@visi.com> wrote: > > The main point is separate the tools from the library. That means each of > Lf5, Chainsaw1, and Chainsaw2 have their own artifacts, separate from > Log4j.jar. That's all. This will make Log4j.jar much smaller (by extracting > Lf5 and Chainsaw1). Only users that specifically want to use the tools will > need to get their appropriate jar. And all will depend upon Log4j.jar. That > really doesn't seem too complex to me. > > > Jake > > On Thu, 31 May 2012 17:15:47 -0400 > Gary Gregory <garydgreg...@gmail.com> wrote: >> My beef is that I do not want 10 jars to pick from, this is a low level >> components, give me one jar to rule them all. Or at least give me the >> option to pick an all-in-one jar. For those who want to save 10KB here and >> there, they can cherry pick I suppose. >> Gary >> On Thu, May 31, 2012 at 3:52 PM, Ralph Goers >> <ralph.go...@dslextreme.com>wrote: >>> Log4j 2 is already a multi-module build. I am not at all sure why you >>> would want to expend all this effort on a 1.3 when 2.0 should be our next >>> target. >>> >>> Ralph >>> >>> On May 31, 2012, at 12:46 PM, Antonio Petrelli wrote: >>> >>> > Hi all >>> > following Christian's rant at Google+: >>> > https://plus.google.com/102440702937210603575/posts/HbD1fa9NGHY >>> > I started forking Log4j at GitHub: >>> > https://github.com/apetrelli/log4j >>> > >>> > The first step I did is providing a stub for a multi-module build. >>> > Assuming that Log4j should be multi-module is fundamental. I don't >>> > want to start a Maven lesson, you can see anywhere about the benefit >>> > of having separated modules with well-identified dependencies. >>> > For now, I have only a parent project (pom type) and a "core" project, >>> > that soon will go on a diet, moving code in other modules. >>> > >>> > About the version, you might notice that I put "1.3.0-SNAPSHOT" >>> > version because, at the end, you will not recognize Log4j 1.2.x >>> > artifacts at all. They will be more numerous, smaller and with >>> > specific dependencies. >>> > >>> > Feel free to discuss or to help via forking. >>> > >>> > Best regards >>> > Antonio >>> > >>> > --------------------------------------------------------------------- >>> > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org >>> > For additional commands, e-mail: log4j-dev-h...@logging.apache.org >>> > >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org >>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org >>> >>> >> -- >> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >> JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0 >> Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-dev-h...@logging.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
