[MASSEMBLY-593] jarsigner plugin failes after assembly plugin

[jira-importer]

Adrian Stabiszewski opened MASSEMBLY-593 and commented

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]

---

Affects: 2.2, 2.2.1, 2.2.2

Attachments:

• maven-assembly.zip (2.38 kB)

1 votes, 3 watchers