maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerome Lacoste (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MJAR-67) jar:sign - Jars containing invalid remains of older signatures won't get signed
Date Sat, 25 Aug 2007 20:48:47 GMT

     [ http://jira.codehaus.org/browse/MJAR-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jerome Lacoste updated MJAR-67:
-------------------------------

    Attachment: MJAR-67.diff

Force the user to add a flag to bypass this issue. Failures cause by signing an already signed
jar should not go unnoticed.

So the exception is thrown by default and a user flag is added to allow bypassing the failed
check.
Finally the log message is a warning instead of info.

> 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, MJAR-67.diff, 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

       

Mime
View raw message