The plugin's signing process can fail, leaving unsigned jars "in place".
Subsequent executions do attempt to sign such jars without a clean.
---------------------------------------------------------------------------------------------------------------------------------------------
Key: MOJO-747
URL: http://jira.codehaus.org/browse/MOJO-747
Project: Mojo
Issue Type: Bug
Components: webstart
Environment: Linux, maven 2.0.6
Reporter: David Corbin
Priority: Minor
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
