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 31530] - jar task creates an empty jar file if <manifest> is specified
Date Tue, 26 Oct 2004 14:31:32 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=31530>.
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=31530

jar task creates an empty jar file if <manifest> is specified

bodewig@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Normal                      |Enhancement



------- Additional Comments From bodewig@apache.org  2004-10-26 14:31 -------
Once you have a manifest, the jar is not empty anymore.  As far as Ant is concerned,
jar files are never empty, so the whenempty attribute doesn't make too much sense.

I only see the option of an additional attribute, I don't see a good candidate to
reuse among the existing attributes.

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


Mime
View raw message