[
https://jira.codehaus.org/browse/MASSEMBLY-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold updated MASSEMBLY-593:
-----------------------------------------
Comment: was deleted
(was: Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.)
> jarsigner plugin failes after assembly plugin
> ---------------------------------------------
>
> Key: MASSEMBLY-593
> URL: https://jira.codehaus.org/browse/MASSEMBLY-593
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2, 2.2.1, 2.2.2
> Reporter: Adrian Stabiszewski
> Attachments: maven-assembly.zip
>
>
> This is a regression since version 2.2-beta-5 where this config is working.
> Workaround for 2.2.2: It works if the "appendAssemblyId" is set to false.
> For me it looks like the jar file is still open by the assembly plugin when
> the jarsigner plugin tries to sign it.
> This becomes visible when you set the option
> "<removeExistingSignatures>true</removeExistingSignatures>" on the jarsigner
> plugin:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jarsigner-plugin:1.2:sign (sign) on project
> demo: Failed to unsign archive
> \bugreports\maven-assembly\target\demo-1.0-SNAPSHOT.jar: Failed to delete
> \bugreports\maven-assembly\target\demo-1.0-SNAPSHOT.jar while trying to
> rename \bugreports\maven-assembly\target\demo-1.0-SNAPSHOT.jar.unsigned ->
> [Help 1]
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
