Glen Daniels writes: > > Sam? Is this because we don't want to force people to move to an un-"official" > log4j release like 1.2? (that rationale doesn't actually seem to work since the > 1.2 classes will shadow the 1.1.3 ones if the new jar is on the classpath first > anyway....) > > ----Original Message----- > From: Mark Volkmann [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 01, 2002 7:51 AM > To: [EMAIL PROTECTED] > Subject: Re: Log4J date in JAR file name > > > C'mon guys. I'm betting there's some good reason why log4j.jar in the interim > drops includes a date in the name. I'd just like to hear what it is. Can someone > please tell me? > > If there is a good reason, why aren't other JARs like clutil and wsdl4j dated? > If there isn't a good reason then I'd like it to be named simply log4j.jar or > log4j-core.jar. > > ----- Original Message ----- > From: Volkmann, Mark > To: '[EMAIL PROTECTED]' > Sent: Thursday, January 31, 2002 8:12 AM > Subject: Log4J date in JAR file name > > What's the rationale for including a date in the log4j.jar file name or the interim > drops?
The answer is actually very simple. The datetime is there because the build for log4j (http://jakarta.apache.org/builds/gump/latest/jakarta-log4j.html) puts it there. What you get with the builds that are posted is a consistent set of jars and you can look at the build log to verify that that this is in fact the case. There certainly are other configurations that make sense for people. One of the most obvious is the milestone build (alphas ant the like). This just happens to be something that I build anyway and make available in case somebody else finds it useful. If others feel like posting other configurations, they are certainly welcome to. - Sam Ruby
