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=14950>. 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=14950 Task signjar defect ------- Additional Comments From [EMAIL PROTECTED] 2002-12-04 17:29 ------- It might be interesting (and helpful) to know if there was a difference between the two forms of signing when you did a jarsigner -verify -verbose <jarfilename> on a file that was signed with ant and on the same file signed with jarsigner. I am not an expert in jar signing, and probably can't do the fixing for this, but I am fiddling around with webstart and was thinking about using the ant task to sign things. Does the ant task appear to sign the jar at all? If webstart is completely refusing to start it I think that means it thinks the jar never got signed at all, or the file appears to be modified since signing. It would be worth checking that you don't do anything to update the jar after it is signed. I notice the documentiation for jar doesn't specify whether update or overwrite is the default behavior for jar task. A doc patch for this would probably be good in any case. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
