On Nov 1, 2012, at 2:13, Ralph Goers <ralph.go...@dslextreme.com> wrote:
So you guys want all these jars in a -all jar? I created the -combined jar because of a couple of emails I got where it was clear the users wanted to use the api and core together and didn't want the flexibility to separate them. Including all the bridges in that jar might actually be less useful as they would be forced to divert all other logging to Log4j. That actually would be a good thing in some cases. Let's say I'm creating an app with lots of dependencies. If those dependencies all use different logging systems, I'm going to get logs all over the place. In the case of our app server, I do want to capture all logging in one place. When something does wrong, I can tell users to turn on debug logging and post the one log file to the issue web site. Does that scenario make sense to you or am I missing a side effect? I don't really have a problem with creating a -all too I suppose as it wasn't a big deal to create it (although I am pretty sure the sources jar that gets created by the release isn't correct right now). That would be good to fix anyway! Aren't we missing some test jars too? I'n not crazy about log4j-api+core.jar just because the + seems odd, although it does make sense. Is the "+" allowed in a file name on all relevant platforms? It's OK on Windows. Unix and Mac? Gary Ralph On Oct 31, 2012, at 6:44 PM, Paul Benedict wrote: +1 for "all" On Oct 31, 2012 8:32 PM, "Gary Gregory" <garydgreg...@gmail.com> wrote: > Hi All: > > I find the name "log4j-combined-2.0-beta3-SNAPSHOT.jar" unhelpful if not > confusing considering we produce: > > api\target\log4j-api-2.0-beta3-SNAPSHOT.jar > combined\target\log4j-combined-2.0-beta3-SNAPSHOT.jar > core\target\log4j-core-2.0-beta3-SNAPSHOT.jar > flume-ng\target\log4j-flume-ng-2.0-beta3-SNAPSHOT.jar > jcl-bridge\target\log4j-jcl-2.0-beta3-SNAPSHOT.jar > log4j12-api\target\log4j12-api-2.0-beta3-SNAPSHOT.jar > slf4j-impl\target\slf4j-impl-2.0-beta3-SNAPSHOT.jar > web\target\log4j-web-2.0-beta3-SNAPSHOT.jar > > So "combined" between what and what? I know it's api and core because I > read that recently around here but it's not crystal clear. How about > calling it log4j-api+core.jar just to be clear? > > But my point really is that I'd prefer not to have to think about which > jars to include and just have a log4j-all.jar. > > In one project I work with we are approaching 100 third party jars. I'd > rather have my Ivy (or Maven) build just say "log4j-all" just like I say > "jetty-all" and "cxf-bundle". > > I know some folks have to worry about moving bytes around and sipping RAM, > but other folks don't, so now that we've made the 'give me lots of little > jars' crowd happy, can we make the 'keep it simple' crowd happy too with a > log4j-all.jar? > > Gary > > -- > 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 >
