+1
--
Tom Jordahl
-Original Message-
From: Glen Daniels [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 01, 2002 9:44 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Log4J date in JAR file name
Personally, I'd like to see a "checkpoint" nightly build which is bui
se we're locked to log4j-1.1.3. I'd be happy to help set this up if
you can point me in the right direction.
--Glen
> -Original Message-
> From: Sam Ruby [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 01, 2002 9:24 AM
> To: [EMAIL PROTECTED]
> Subject: RE:
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
asspath first anyway)
-Original Message-From: Mark Volkmann
[mailto:[EMAIL PROTECTED]]Sent: Friday, February 01, 2002 7:51
AMTo: [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 interi
Title: 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
