Feature Request: Please version the library(ies)

[gregorypierce]

It would be beneficial for deployment and maint. if JBossCache (and indeed all JBoss libraries) adopted a versioning of the .jar files so that IT folks will be able to ensure proper versioning of applications in production environments.

jboss-cache-1.2.3.jar is easier to check the deployed version of jboss-cache.jar. Especially if its shared amongst multiple applications.

[goodchiller]

the versioning of used jars like 'jboss-aop.jar' could be helpful, too...

[ben.wang]

This is a bigger question to ask then JBossCache forum. :-)

But for JBossCache (same for JGroups), you can find out the version of the library by java -cp jboss-cache.jar org.jboss.cache.Version

-Ben

[gregorypierce]

Oh I'm sure. I'm here in Atlanta though, want me to go find Marc and smack him up some :)

Nevertheless, what's a good place to start requesting this level of feature as I think it is something very beneficial to the JBoss products as a whole.

[adrian.brock]

The version number should be in the manifest not the jar name.
Use JIRA to raise feature requests.

e.g. the new build does this automatically if there is no explicit manifest

 <!-- Create a jar archive
 Jars the inputs of the jar artifact
 -->
 <jar null="@{manifest}">
 <mkdir dir="@{parentDir}"/>
 <jar destfile="@{output}">
 <manifest>
 <attribute name="Created-by" value="@{component.VMVersion} @{component.VMVendor}"/>
 <attribute name="Specification-Title" value="@{component.specTitle}"/>
 <attribute name="Specification-Version" value="@{component.specVersion}"/>
 <attribute name="Specification-Vendor" value="@{component.specVendor}"/>
 <attribute name="Implementation-Title" value="@{component.implTitle}"/>
 <attribute name="Implementation-URL" value="@{component.implURL}"/>
 <attribute name="Implementation-Version" value="@{component.implVersion}"/>
 <attribute name="Implementation-Vendor" value="@{component.implVendor}"/>
 <attribute name="Implementation-Vendor-Id" value="@{component.implURL}"/>
 <attribute name="Class-Path" value="@{classpath}"/>
 </manifest>
 <filesets/>
 </jar>
 </jar>

[gregorypierce]

If that's the decision you guys have made that's fine. Whenever our sysdamins need to version applications across multiple machines its always a problem. We'll just rename them on our end for now because once its all compiled, no one is going to be reading the inside of a manifest file and most admins's eyes glaze over when you tell them this :)