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=29085>. 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=29085 Timestamps in jar-Manifest [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[EMAIL PROTECTED] Component|Core |Core tasks ------- Additional Comments From [EMAIL PROTECTED] 2004-06-05 19:50 ------- This would be useful. netbeans.org has a generic script that uses something like <tstamp> <format property="buildnumber" .../> </tstamp> <jar jarfile="..." manifest="${some-basic-manifest}"> <manifest> <!-- various important fixed attributes... then: --> <attribute name="Impl-Version" value="${buildnumber}"/> </manifest> <fileset .../> </jar> Currently the JAR is always rebuilt, which is annoying and slows down the build. Possible workaround would be to create a temporary manifest somewhere using <manifest> with everything but the Impl-Version set to "@BUILD-NUMBER@", then <copy> with a filter, then make the JAR; cumbersome. I could probably supply a patch for this if committers would be interested in applying it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
