[
https://issues.apache.org/jira/browse/MJAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957199#comment-17957199
]
Matthias Bünger commented on MJAR-116:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-jar-plugin#288|https://github.com/apache/maven-jar-plugin/issues/288].
> Allow signing of already signed jars
> ------------------------------------
>
> Key: MJAR-116
> URL: https://issues.apache.org/jira/browse/MJAR-116
> Project: Maven JAR Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: sign
> Reporter: Pavel Jisl
> Assignee: Benjamin Bentmann
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
