[
http://jira.codehaus.org/browse/MWEBSTART-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerome Lacoste closed MWEBSTART-34.
-----------------------------------
Assignee: Jerome Lacoste
Resolution: Fixed
Fixed on trunk.
$ svn commit -m "MWEBSTART-34 prevent failures in the signing process to leave
unsigned jars in place. Solved by using an alternate temporary unsigned file
instead of doing the signing fully in place. This should also solve
MWEBSTART-28 as side effect."
Sending plugin/pom.xml
Sending
plugin/src/main/java/org/codehaus/mojo/webstart/AbstractBaseJnlpMojo.java
Sending
plugin/src/main/java/org/codehaus/mojo/webstart/AbstractJnlpMojo.java
Sending
plugin/src/main/java/org/codehaus/mojo/webstart/JarSignMojoConfig.java
Transmitting file data ....
Committed revision 5684.
Note that this requires a pached (thus unpublished) snapshot of the jar plugin.
Vote for MJAR-84 if you want it !
> The plugin's signing process can fail, leaving unsigned jars "in place".
> Subsequent executions do attempt to sign such jars without a clean.
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MWEBSTART-34
> URL: http://jira.codehaus.org/browse/MWEBSTART-34
> Project: Maven 2.x Webstart Plugin
> Issue Type: Bug
> Affects Versions: 1.0-alpha-1, 1.0-alpha-2
> Environment: Linux, maven 2.0.6
> Reporter: David Corbin
> Assignee: Jerome Lacoste
> Priority: Minor
> Fix For: 1.0-alpha-2
>
> Attachments: MJAR_MWEBSTART-34_support_plus_MJAR-67.diff,
> MWEBSTART-34.diff, MWEBSTART-34.diff,
> webstart-maven-plugin-1.0-alpha-2-SNAPSHOT.jar
>
>
> If the jar signing process fails, the jars are left in the target/jnlp
> directory unsigned. The next execution examines the timestamps and decides
> incorrectly that the jar files don't need to be signed.
> The easiest way to create the problem, is to specify a bad keystore.
> One solution would be to "get" the jars to an alternate name "foo-1.0.jar" ->
> "foo-1.0.jar-unsigned", and then have the jarsigner copy and sign together
> (which I *think* it can do).
--
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
