![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Unassigned |
|
Components:
|
sign |
|
Created:
|
14/Nov/12 7:31 AM
|
|
Description:
|
Our application has a very large number of 3rd party jars which need to be signed. At the moment the sign option appears to re-sign the jars every build, which is a very slow process. Can there not be some way to have a "cache" of signed jars that can be used for subsequent builds.
In our old ant days, we just md5ed our lib directory and only resigned if the md5 from the last build differed from the md5 of the current unsigned jars
|
|
Project:
|
Maven 2.x Webstart Plugin
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Will Tatam
|
|
|
|
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
