Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: 2.1
-
Component/s: None
-
Labels:None
Description
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
Issue Links
- is depended upon by
-
MWEBSTART-88
HttpJarSignClient - New goal "httpsign" which will sign jar files by submitting them to a signing service via HTTP Post
-
- is superceded by
-
MWEBSTART-18
Allow different pluggable jar signers to be used
-
Please apply