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=37259>. 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=37259 Summary: whenempty option for jar task should be smarter Product: Ant Version: 1.6.5 Platform: PC OS/Version: other Status: NEW Severity: normal Priority: P3 Component: Build Process AssignedTo: dev@ant.apache.org ReportedBy: [EMAIL PROTECTED] If you use the whenempty="fail" attribute for the jar task, ant will print out the following message: [jar] JARs are never empty, they contain at least a manifest file Perhaps it would make a tad more sense if this option would cause the build to fail if there were no other files than the manifest. That way, we could use this feature to cause the build to fail if, say, there were no *meaningful* files in the archive, because a project build failed entirely after a clean. I wouldn't get too hung up on the meaning of "existence" here. Perhaps implement something sensible so that this options isn't so utterly retarded that it causes programmers to wonder why it was put there at all. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
