Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@xml.apache.org
Message-ID: <CB1FF0A474AEA84EA0206D5B05F6A4CB26E013@S1001EXM02.macromedia.com>
From: Glen Daniels <gdaniels@macromedia.com>
To: "'axis-dev@xml.apache.org'" <axis-dev@xml.apache.org>
Subject: RE: Log4J date in JAR file name
Date: Fri, 1 Feb 2002 09:44:27 -0500 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Personally, I'd like to see a "checkpoint" nightly build which is built =
with exactly the jars in lib/, and then a separate "bleeding-edge" =
build.... There have been several occasions where we've wanted to =
switch to a nightly but had to rebuild ourselves because 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:rubys@us.ibm.com]
> Sent: Friday, February 01, 2002 9:24 AM
> To: axis-dev@xml.apache.org
> Subject: RE: Log4J date in JAR file name
>=20
>=20
> Glen Daniels writes:
> >
> > Sam?=A0 Is this because we don't want to force people to move=20
> to an  un-"official"
> > log4j release like 1.2?=A0 (that rationale doesn't actually =20
> seem to work since the
> > 1.2 classes will shadow the 1.1.3 ones if the new jar is =20
> on the classpath first
> > anyway....)
> >
> > ----Original Message-----
> > From: Mark Volkmann  [mailto:volkmann2@charter.net]
> > Sent: Friday, February 01, 2002 7:51  AM
> > To: axis-dev@xml.apache.org
> > Subject: Re: Log4J date in  JAR file name
> >
> >
> > C'mon guys. I'm betting there's some good reason  why=20
> log4j.jar in the interim
> > drops includes a date in the name. I'd just like  to hear=20
> what it is. Can someone
> > please tell me?
> >
> > If there is a good reason, why aren't other JARs  like=20
> clutil and wsdl4j dated?
> > If there isn't a good reason then I'd  like=A0it to be named=20
> simply log4j.jar or
> > log4j-core.jar.
> >
> > ----- Original Message -----
> > From:  Volkmann, Mark
> > To: 'axis-dev@xml.apache.org'
> > 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=20
> file name or the interim
> > drops?
>=20
> The answer is actually very simple.  The datetime is there because =
the
> build for log4j
> (http://jakarta.apache.org/builds/gump/latest/jakarta-log4j.ht
ml) 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