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 29683] New: - Jar task with zipgroupfileset always builds the jar file
Date Fri, 18 Jun 2004 21:45:37 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=29683>.
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=29683

Jar task with zipgroupfileset always builds the jar file

           Summary: Jar task with zipgroupfileset always builds the jar file
           Product: Ant
           Version: 1.6.1
          Platform: All
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: ken.corbin@hp.com


The jar task which contains a nested zipgroupfileset element, and does not 
specify an external manifest file, will always rebuild the jar file, even if 
it is up to date.  Apparently an internal manifiest file is constructed, and 
its date checked against that of the jar file, which will always be out of 
date.   The following snipped is one that always builds the jar file, but it
starts behaving normally when I add an manifest parameter.

<jar destfile="${outdir}/CountServer.jar">
    <zipfileset dir="${classdir}" includes="**/*.class"/>
    <zipgroupfileset refid="libraries"/>
</jar>

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


Mime
View raw message