[
http://jira.codehaus.org/browse/MWEBSTART-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211520#action_211520
]
Karl M. Davis commented on MWEBSTART-144:
-----------------------------------------
I'm guessing that this is actually a duplicate of
http://jira.codehaus.org/browse/MWEBSTART-132. At least, unsetting that option
fixed the problem for me.
> Jar Unsigning Does Not Work
> ---------------------------
>
> Key: MWEBSTART-144
> URL: http://jira.codehaus.org/browse/MWEBSTART-144
> Project: Maven 2.x Webstart Plugin
> Issue Type: Bug
> Components: sign
> Affects Versions: 1.0-alpha-2
> Environment: Windows XP, JDK 1.6.0_17
> Reporter: Joseph Hitt
>
> If I deploy the application as a signed applet, I can get everything to work
> perfectly, possibly applets are less picky about signatures(?) However, as a
> JNLP application - I keep getting:
> #### Java Web Start Error:
> #### JAR resources in JNLP file are not signed by same certificate
> This tells me that the unsign feature is either not stripping the
> pre-existing signature, or perhaps using two different signatures to sign
> dependencies. I have tried both:
> <unsignAlreadySignedJars>true</unsignAlreadySignedJars>
> and
> <unsign>true</unsign>
> under the <configuration> level.
> It should also be noted that I have two poms - one pom that is dependent upon
> another, but jars for the webstart app coming from both projects. Is it
> possible that different signatures are being used for each of these?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
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
