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=20179>. 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=20179 Inline manifest causes jar to be rebuilt too often [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2003-05-23 13:54 ------- I respectfully disagree. Quoting from the Ant documentation: "When using inline manifests, the Jar task will check whether the build file is more recent that the Jar file when deciding whether to rebuild the Jar. This will not take into account property file changes which may affect the resulting Jar." Although it doesn't explicitly say what happens when property values set by the tstamp task are used, I think it's fair to say that the second sentence above hints that property values are not considered. I think that the documented behaviour, as I interpret it, is preferable. Your suggested solution just moves the problem to the manifest task, and I would still have to work around the problem with uptodate checks. Also, there are several examples in the Ant documentation where tstamp created properties such as ${TODAY} are used with the "Implementation-Version" attributes. As the examples are written, they would cause a rebuild at leas once a day. I hope that I'm completely wrong (or out cycling as we say in Sweden) and that there is a simple way to get the current time into the manifest without uptodate checks, but I really can't think of one!
