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|REOPENED |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2003-05-27 04:48 ------- I have updated the documentation. It was wrong. I will disagree that the previous documentation described preferable behaviour. You are presenting to the <jar> task a manifest specification which contains different values from those in manifest of the existing Jar file. You want this manifest specification to be ignored. I don't think that is correct. The previous behaviour was incorrect and undesirable. If you don't want to rebuild the jar, don't present the jar task with different contents (which is effectively what you are doing). i.e Store the manifest in a file and update it in a separate target. You can trigger updating whenever you explicitly invoke that target or delete the manifest, perhaps as part of a clean target.
