[ http://jira.codehaus.org/browse/MJAR-35?page=all ]
Brett Porter closed MJAR-35:
----------------------------
Assign To: Brett Porter
Resolution: Won't Fix
moved to MOJO, as I understand it
> Abstraction for JarSignMojo so that webstart plugin can allow the user to
> choose how their jars are signed
> ----------------------------------------------------------------------------------------------------------
>
> Key: MJAR-35
> URL: http://jira.codehaus.org/browse/MJAR-35
> Project: Maven 2.x Jar Plugin
> Type: New Feature
> Reporter: David Boden
> Assignee: Brett Porter
> 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 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
