You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2003/05/23 12:49:10 UTC
DO NOT REPLY [Bug 20179] New: -
Inline manifest causes jar to be rebuilt too often
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
Summary: Inline manifest causes jar to be rebuilt too often
Product: Ant
Version: 1.5.1
Platform: Other
OS/Version: Other
Status: NEW
Severity: Major
Priority: Other
Component: Core tasks
AssignedTo: dev@ant.apache.org
ReportedBy: gunnar.grim@ninetech.se
When an inline manifest element is used, the dependency checking gets confused.
According to the documentation, the jar should be rebuilt if any dependent file
has been changed, including the build.xml itself. That is fine, but if an
expanded property used within the manifest element causes the resulting manifest
to be different from the one in the jar, the jar is rebuilt. I have an inline
manifest where the implementation version is constructed from properties
including one that is the time of day in hours and minutes. If at least one
minute has passed since the last rebuild, the jar is rebuilt again. This
behaviour makes it practically impossible to include build date and time in the
manifest.