You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2007/08/25 22:13:48 UTC
[jira] Updated: (MJAR-51) handle signing jars which are not project
artifacts and not "in place" signing
[ http://jira.codehaus.org/browse/MJAR-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MJAR-51:
--------------------------------
Component/s: sign
> 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
>
> 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