ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 29085] New: - Timestamps in jar-Manifest
Date Wed, 19 May 2004 12:22:47 GMT
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=29085>.
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=29085

Timestamps in jar-Manifest

           Summary: Timestamps in jar-Manifest
           Product: Ant
           Version: 1.6.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core
        AssignedTo: dev@ant.apache.org
        ReportedBy: daniel.estermann@adnovum.ch


Currently, a jar-file is updated if one of the manifest entries changes.
If an entry contains the build-time, I don't want the jar to be rewritten every
time i build the project. The build-time entry should just be updated if
anything else in the jar changed.

I propose to introduce a new flag (named 'forceupdate' or similar) for a
manifest attribute. That flag tells wether the entry must be compared with the
old state or if a possible change should be ignored. 

<manifest>
  <attribute
    name="Build-Stamp"
    value="${DSTAMP}${TSTAMP}"
    forceupdate="false"/>
</manifest>

Implementation: 
A logical and simple solution is to change the Manifest.equals method to ignore
the selected entries. However, i do not know if this affects other tasks.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message