[mojo-dev] [jira] (MWEBSTART-211) Building with JDK 1.7 causes "invalid SHA1 signature" error

[Jeroen Peelaerts (JIRA)]

Jeroen Peelaerts commented on MWEBSTART-211 Building with JDK 1.7 causes "invalid SHA1 signature" error I have been facing the same problem after upgrading to jdk1.7_21. I checked the release notes and it seems that the java webstart client that is included treats signed artifacts differently. They added a note that self-signed ceritificates might be refused by default in the future. http://www.oracle.com/technetwork/java/javase/7u21-relnotes-1932873.html#apsign The issue only occured with jars that were already signed and had SHA-1 digests in their MANIFEST.MF (in this case eclipselink 2.5 jars from the maven central). After removing this information, the packaged application booted fine. This digest was then replaces by a SHA-256 one by the webstart plugin. That's why I think this is more a matter of unsigning the jars first and the resigning them. Did you have this option enabled? Be aware that it might not work in combination with using the libPath parameter, as mentioned in http://jira.codehaus.org/browse/MWEBSTART-132 , so you would need to try the bleeding edge of the plugin. I will give it a whirl when I find the time..

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email