You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/20 15:00:00 UTC
[jira] [Updated] (MASSEMBLY-593) jarsigner plugin failes after
assembly plugin
[ https://issues.apache.org/jira/browse/MASSEMBLY-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliotte Rusty Harold updated MASSEMBLY-593:
--------------------------------------------
Priority: Minor (was: Major)
> jarsigner plugin failes after assembly plugin
> ---------------------------------------------
>
> Key: MASSEMBLY-593
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-593
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2, 2.2.1, 2.2.2
> Reporter: Adrian Stabiszewski
> Priority: Minor
> 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
(v8.3.4#803005)