[ http://jira.codehaus.org/browse/MJAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MJAR-116. ---------------------------------- Assignee: Benjamin Bentmann Resolution: Won't Fix The jarsigner related goals in this plugin will be deprecated, please use the dedicated [maven-jarsigner-plugin|http://maven.apache.org/plugins/maven-jarsigner-plugin/] which allows to sign a single JAR multipe times. > Allow signing of already signed jars > ------------------------------------ > > Key: MJAR-116 > URL: http://jira.codehaus.org/browse/MJAR-116 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement > Components: sign > Reporter: Pavel Jisl > Assignee: Benjamin Bentmann > Attachments: JarSignMojo-forcesign-patch.txt > > > For releasing webstart applications is crucial to have all jars included > signed with one certificate of the releasing company. If these jars are not > signed with one unified certificate, Java Webstart system asks for each > unsigned (or jar with another signature) if user agrees and grants access to > the system. > Maven Jar Plugin currently does not support signing of already signed > packages. I created patch, that creates new property "forcesign" which > default value is false (standard behavior) and if this property is set to > true, plugin will continue with signing. -- 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