[
http://jira.codehaus.org/browse/MJAR-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MJAR-51.
----------------------------
Assignee: Olivier Lamy
Resolution: Duplicate
Fix Version/s: 2.2
Have a look at the issue MJAR-84 and the new field skipAttachSignedArtifact
(this should help :-) )
> handle signing jars which are not project artifacts and not "in place" signing
> ------------------------------------------------------------------------------
>
> Key: MJAR-51
> URL: http://jira.codehaus.org/browse/MJAR-51
> Project: Maven 2.x Jar Plugin
> Issue Type: Improvement
> Components: sign
> Affects Versions: 2.1
> Reporter: Scott Cytacki
> Assignee: Olivier Lamy
> Fix For: 2.2
>
>
> It seems the SignJarMojo is intended to be used both as a way to sign a jar
> artifact, and as a utitlity to sign jars for other plugins in maven.
> The jnlp plugin uses it in the latter mode. However currently it can only
> sign jars "inplace" when the jar being signed isn't a artifact of a project.
> More specifically if the signedJar field is not null, and the project of the
> SingJarMojo is null, then SignJarMojo fails. Changing:
> else
> {
> project.getArtifact().setFile( signedjar );
> }
> to
> else if ( project != null)
> {
> project.getArtifact().setFile( signedjar );
> }
> Would fix this.
--
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
