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 9163] New: - Jar task always updates
Date Thu, 16 May 2002 15:45:07 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9163>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9163

Jar task always updates

           Summary: Jar task always updates
           Product: Ant
           Version: 1.5Beta1
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core tasks
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: wr0ngway@yahoo.com


If update="true", The jar task always updates the jar if a nested manifest is
specified.  It seems that when update is true, the zip task renames the old jar,
but calls isUpToDate() with the original unrenamed jar, so the jar task can't
find the manifest as the jar it is given doesn't exist - perhaps the zip task
should pass the renamed file to isUpToDate()

e.g.
<jar jarfile="foo.jar" update="true">
  <manifest>
    <attribute name="foo-ver" value="1.0"/>
  </manifest>
</jar>

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


Mime
View raw message