thanks for the response. this assumes there are two files. the original jar and the signed jar. i guess it wouldn't be possible with two seperate files. i was hoping that there was a feature that i may have missed to accomplish this with signjar. :)
michael -----Original Message----- From: Dominique Devienne [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 02, 2002 2:15 PM To: 'Ant Users List' Subject: RE: signing jar only if it has been updated Right after you perform signjar, touch a file that acts as the timestamp for the last time you performed signjar. Then have your signjar target depend on a check-jar-up2date-4signjar target that uses <uptodate> between the jar and the timestamp file, setting a property if it need (or not) updating, and have the signjar target if/unless on that property. I'll leave the actual implementation to you ;-) Try it, and if you're stuck I can help some more, and someone not as lazy as me if going to provide you the full solution. --DD -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 02, 2002 3:17 PM To: [EMAIL PROTECTED] Subject: signing jar only if it has been updated would anyone out there know how to accomplish this? it seems that the signjar task signs a jar file regardless if it has changed. this takes quite a long time if the jar file is large. thanks, mike -- 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]>
