Sam Ruby wrote:
>
> Additionally, I would be in favor of standardizing - even if it is only
> across jakarta projects - a mechanism for embedding the version number in a
> standard location inside the jar file itself.
>
I have a suggestion for how to approach this one.
The JDK 1.3 docs describe a convention for defining the product name and version
number of a package included in a JAR file, plus the dependencies of that JAR
file on specific versions of external JARs -- all done in the
META-INF/MANIFEST.MF file. A 2.3 container (like Tomcat 4.0) is even required
to enforce checking for availability of the dependent JARs when you include
depenencies in your WEB-INF/lib/*.jar files.
It's worth taking a look at this.
http://java.sun.com/j2se/1.3/docs/guide/extensions/versioning.html
>
> - Sam Ruby
Craig
