Indeed. See http://marc.theaimsgroup.com/?l=ant-user&m=102046298307827&w=2 . And the way around this problem I described is still valid I think. Another way around it would be to keep the both the sign and unsigned jar around, but then you would have to be careful not to use both in the same classpath.
--DD -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 14, 2002 10:18 AM To: [EMAIL PROTECTED] Subject: RE: Preventing a JAR From Being Signed Twice the signjar task only compares the timestamp between the signed jar and the original jar. if you don't specify the signedjar attribute then the original jar is overwritten, and signjar has nothing to compare it to. thus, signjar will sign the jar again. i just ran into this problem a couple of weeks back. -----Original Message----- From: Holger Rauch [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 14, 2002 12:16 AM To: [EMAIL PROTECTED] Subject: Preventing a JAR From Being Signed Twice Hi! Is there any way for the <signjar> task to detect whether a JAR file has already been signed? If not, is that at all possible? If so, how can it be done? (I do not want to risk a JAR file being signed twice.) Any help will be greatly appreciated! Greetings, Holger -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
