[
https://issues.apache.org/jira/browse/MJAR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957133#comment-17957133
]
Matthias Bünger commented on MJAR-35:
-------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-jar-plugin#223|https://github.com/apache/maven-jar-plugin/issues/223].
> Abstraction for JarSignMojo so that webstart plugin can allow the user to
> choose how their jars are signed
> ----------------------------------------------------------------------------------------------------------
>
> Key: MJAR-35
> URL: https://issues.apache.org/jira/browse/MJAR-35
> Project: Maven JAR Plugin (Moved to GitHub Issues)
> Issue Type: New Feature
> Reporter: David Boden
> Assignee: Brett Porter
> Priority: Major
> Attachments: JarSignerMojo.java, MJAR-35.diff,
> lehmanjarsigner-1.0-src.zip
>
>
> The webstart Maven 2 plugin signs jar files as part of its operation. At the
> moment, it relies upon JarSignMojo to do this.
> While this is going to be correct 90% of the time, sometimes users (like
> myself!) need to ask the webstart plugin to sign jars in a different way.
> Specifically, my company keeps its private key separate and provides an HTTP
> Post interface to allow me to submit jars for signing. I've got a Mojo to do
> this.
> What I need is for the webstart plugin to use an abstraction defined in an
> interface called JarSignerMojo (attached to this issue) rather than
> JarSignMojo. That way, I can plug my own Mojo in to be used instead of
> JarSignMojo. Jerome Lacoste is doing the webstart plugin development and is
> happy to accommodate this change if we can get the interface added to the jar
> plugin project.
> The only change to the existing code is that JarSignMojo's class declaration
> needs to be changed to:
> public class JarSignMojo extends AbstractMojo implements JarSignerMojo
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
