I have a related question.
Its it possible to create the manifest for a jar on the fly somehow?
The reason is to add a timestamp inside the JAR for versioning?
something like:
<jar destfile="foo.jar"
basedir="bar">
<manifest version="${TIMESTAMP}"/>
</jar>
Use the manifest task to create your manifest on the fly.
You will need to create an attribute that will contain the timstamp, for instance you can call this attribute "TimeStamp".
To get this information from a running java application you would need to use the Manifest class returned from the JarFile class. This is all part of the java.util.jar package.
-----Original Message----- From: Rebhan, Gilbert [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 05, 2003 11:21 AM To: ant_user (E-Mail) Subject: Versioning / Manifest
Hi,
Scenario :
A Client/Server Application is distributed as a bunch of Jar's.
Client and Server have an XML-File that contains the versioninfo for these Jar's.
The Jar's of a new release are transfered to the server, the xml-File is manually created.
Question 1 : How to automate the creation of that xml-File ?
After starting the client, the client-xml is compared to the server-xml. The new Jar's are then transfered to the client.
Question 2 : Is there a chance to transfer only the altered/newer class-Files instead of the whole Jar as bandwidth is limited ?
I guess there's a way via the Manifest. If versioning is possible with the Manifest itself maybe we don't need that xml-file anymore ?
Best practices ?
thx for any advice !!
bye4now, Gilbert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
