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-67) jar:sign - Jars containing invalid
remains of older signatures won't get signed
[ http://jira.codehaus.org/browse/MJAR-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MJAR-67:
--------------------------------
Component/s: sign
> jar:sign - Jars containing invalid remains of older signatures won't get signed
> -------------------------------------------------------------------------------
>
> Key: MJAR-67
> URL: http://jira.codehaus.org/browse/MJAR-67
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
> Components: sign
> Affects Versions: 2.1
> Environment: Maven 2.0.4 on Windows XP
> JDK 1.5.0_08
> Reporter: Gottfried Ganßauge
> Attachments: error.log, jar-plugin.patch, pom.xml
>
>
> I'm trying to ease the burden of applet deployment by integrating every dependency of that applet into the applet's .jar archive.
> For this purpose I'm using the unpack goal of the dependency plugin (see attached POM).
> For a particular case I had to integrate an already signed applet.
> There is no way I can get the integrated jar signed using jar:sign - I always get an error from jarsigner (see attached error.log).
> The problem seems to be that jarsigner is called with -verify - although I'm explicitely turning it of in plugin configuration.
> When calling jarsigned from the command line without -verify it runs to completion.
> When running it with -verify from the command line the same error occurs as in the maven build.
--
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