using "Implementation-Version" in MANIFEST.MF to version war, jar and ear files

T

thebad1

Hi,

We are currently going through the process of asking our java
developers and external vendors to stick to a versioning convention
for the various war, jar and ear files that are deployed.

The idea has been suggested that we should have the vendor/developer
ship a "release" file with version information in the root of the
archive file. However I am thinking that there is a standard
versioning specification, as most published libraries include a
"Implementation-Version" attribute in the MANIFEST.MF. But I can't
seem to find a specification or reference for it. I guess that I might
just be searching for a topic for which there is a lot of competition
for keywords... :-(

If Anyone has any ideas on where I can find information on this, I
would be grateful.

Thanks,

T.
 
D

Daniel Dyer

Hi,

We are currently going through the process of asking our java
developers and external vendors to stick to a versioning convention
for the various war, jar and ear files that are deployed.

The idea has been suggested that we should have the vendor/developer
ship a "release" file with version information in the root of the
archive file. However I am thinking that there is a standard
versioning specification, as most published libraries include a
"Implementation-Version" attribute in the MANIFEST.MF. But I can't
seem to find a specification or reference for it. I guess that I might
just be searching for a topic for which there is a lot of competition
for keywords... :-(

<http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#Manifest
Specification>

Dan
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,755
Messages
2,569,536
Members
45,011
Latest member
AjaUqq1950

Latest Threads

Top