https://issues.apache.org/bugzilla/show_bug.cgi?id=29097
Tony Strauss <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
| |ns.com
--- Comment #10 from Tony Strauss <[EMAIL PROTECTED]> 2008-12-03 22:32:03 PST
---
I think that there is an additional problem with signjar's dependency checking.
In particular, if the signed jar is a different file than the unsigned jar,
signjar will recreate the signed jar if its modification time is the *same* as
that of the unsigned jar. This leads to the following pattern:
Build #1:
Build unsigned jar
Build signed jar
Build #2
Build signed jar (because the signed and unsigned jars created in Build #1 have
the same timestamp).
Build #3
Nothing (because Build #2's signed jar has a later modification timestamp than
Build #1's unsigned jar).
This bug means that using signjar's preservelastmodified attribute results in
the jar always being rebuilt.
I think that the correct behavior (followed by the copy task, for instance) is
for signjar to rebuild if and only if the unsigned jar's modification time is
later than that of the signed jar.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
