maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Hart (JIRA)" <>
Subject [jira] Commented: (MJAR-24) don't sign already signed jars (also allow for in-place jar signing)
Date Thu, 12 Mar 2009 17:59:13 GMT


Andrew Hart commented on MJAR-24:

I know this is an old issue, but why is it this way?  For example, suppose I have an already
signed jar and I want to add another signer to the jar.  This is currently causing me a little
bit of grief.

To elaborate:  my understanding is that if I have a secure applet, all of the jars need to
be signed by the same signer.  This applet uses several jar files, including one from the
Nasa WorldWind project which is signed by Nasa.  My applet is signed by me, but I also want
to sign the nasa jar so that all of the jars used by the applet are signed by the same signer.
 A jar file may have multiple signers.  

In looking at the docs for this plugin, I don't see any way to force the plugin to sign (add
another signer) to an already signed jar.


> don't sign already signed jars (also allow for in-place jar signing)
> --------------------------------------------------------------------
>                 Key: MJAR-24
>                 URL:
>             Project: Maven 2.x Jar Plugin
>          Issue Type: Improvement
>            Reporter: Jerome Lacoste
>            Assignee: Kenney Westerhof
>            Priority: Critical
>             Fix For: 2.1
>         Attachments: jarsign-skipsignedjars.diff, MJAR-24-v2.diff
> Patch by Richard Allen <>
> Documentation by Jerome Lacoste (
> - allows for in-place signing of the jar.
> - avoid signing the jar twice.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message