[
http://jira.codehaus.org/browse/MJAVADOC-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171425#action_171425
]
Benjamin Bentmann commented on MJAVADOC-228:
--------------------------------------------
I'm not sure whether it's the right approach to have each and every packaging
plugin deal with JAR signing. This looks like an independent task to me that
could as well be handled by a dedicated maven-signer-plugin. I imagine this
maven-signer-plugin being bound into the "package" phase and to take a fileset
parameter as input or more smarter grab the (attached) artifacts from the
current project and do its job. Assuming one would sign all the project JARs
with the same key, the central configuration of this plugin also should fit the
bill better than using properties to sync the signing config in several JAR
producing plugins.
> Please add support for signing javadoc jar files.
> -------------------------------------------------
>
> Key: MJAVADOC-228
> URL: http://jira.codehaus.org/browse/MJAVADOC-228
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Wish
> Affects Versions: 2.5
> Environment: Maven version: 2.0.10
> Java version: 1.5.0_17
> OS name: "linux" version: "2.6.29" arch: "i386" Family: "unix"
> Reporter: Christian Schulte
>
--
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
