jira-importer commented on issue #958: URL: https://github.com/apache/maven-javadoc-plugin/issues/958#issuecomment-2957364854
**[Benjamin Bentmann](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bentmann)** commented 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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
