DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31410>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31410 build.number forces jars to always rebuild Summary: build.number forces jars to always rebuild Product: Ant Version: 1.6.2 Platform: All OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Using {build.number} in the manifest of a jar file (e.g. in the Implementation- Version attribute) causes that jar file to always rebuild even if nothing else has changed. I have created a modified version of the Jar task with two changes: 1. Manifest comparison ignores the most minor component of the Implementation- Version attribute. Actually it strips off any trailing digits until it reaches the last non digit character in the version and then compares what is left. This means that more significant changes in the version do still result in a new jar file. 2. If the Implementation-Version attribute of the proposed new manifest exists, and ends with "{build}", then {build} is replaced by a build number. If there is an existing jar file and the prefix of the Implementation-Version matches the new one, then the build number is one more than the old value, otherwise the build number is 1. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
