.
Never looked back, had a continual nightmare with fixed classpaths.
-Original Message-
From: Glen Daniels [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 21, 2002 5:03 PM
To: '[EMAIL PROTECTED]'
Subject: RE: version numbers in jars
Alas, this doesn't work in Windows
The following is from http://www.ibiblio.org/java/#recent
I have a request to make of the log4j team, as well as all the other
Java programmers at the Apache Project, IBM alphaWorks, Sun, and
everyone else who distributes JAR archives. Could you please attach a
version number to all your JARs?
: Thursday, February 21, 2002 4:12 AM
To: Jakarta General List
Cc: [EMAIL PROTECTED]
Subject: RE: version numbers in jars
The following is from http://www.ibiblio.org/java/#recent
I have a request to make of the log4j team, as well as all the other
Java programmers at the Apache Project
At 8:27 AM -0500 2/21/02, Glen Daniels wrote:
Axis contains an org.apache.axis.Version class, which has a
getVersionString() method and a main() which prints the version info
to System.out. The version string comes from a resource file, and
is automatically updated by our ant build each time
information the same way, but I would rather not make that via the filename.
--Glen
-Original Message-
From: Elliotte Rusty Harold [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 21, 2002 9:15 AM
To: [EMAIL PROTECTED]
Subject: RE: version numbers in jars
At 8:27 AM -0500 2/21
which
.jar is in use ;)
-Original Message-
From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 21, 2002 11:46 AM
To: [EMAIL PROTECTED]
Subject: RE: version numbers in jars
Oh, I misunderstood what you were wanting.
A big -1 to naming all jars with version #s. I
At 11:29 AM -0500 2/21/02, Glen Daniels wrote:
Oh, I misunderstood what you were wanting.
A big -1 to naming all jars with version #s. I can't think of a
bigger pain in the keister than having to revamp my classpath
settings every time a library revs.
You're still using the classpath for
[Elliotte Rusty Harold]
You're still using the classpath for jars? I only do that when I want
to change the classpath on a per-run basis, in which case I am
changing it and using the version number is not a problem. However,
for standard libraries like xerces.jar that are shared among
Thomas B. Passin wrote:
[Elliotte Rusty Harold]
You're still using the classpath for jars? I only do that when I want
to change the classpath on a per-run basis, in which case I am
changing it and using the version number is not a problem. However,
for standard libraries like xerces.jar that
[Berin Loritsch]
Thomas B. Passin wrote:
[Elliotte Rusty Harold]
You're still using the classpath for jars? I only do that when I want
to change the classpath on a per-run basis, in which case I am
changing it and using the version number is not a problem. However,
for standard
Thomas B. Passin wrote:
[Berin Loritsch]
Thomas B. Passin wrote:
any given app finds the right version?
For some jars like Xerces/Xalan, if you code to the plugable API (aka
JAXP), you only need to upgrade the jar--no recompilation or refactoring
needed.
For others, like the Commons
[Elliotte Rusty Harold]
If all those versions are in the ext directory, how do you make sure that
any given app finds the right version?
They aren't. I put in the one I need.
--
+---++---+
| Elliotte Rusty Harold | [EMAIL
code simultaneously when you need to
change one.
Never looked back, had a continual nightmare with fixed classpaths.
-Original Message-
From: Glen Daniels [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 21, 2002 5:03 PM
To: '[EMAIL PROTECTED]'
Subject: RE: version numbers in jars
13 matches
Mail list logo
