Uploaded image for project: 'Maven Assembly Plugin'
  1. Maven Assembly Plugin
  2. MASSEMBLY-593

jarsigner plugin failes after assembly plugin

    Details

    • Type: Bug
    • Status: Reopened
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.2, 2.2.1, 2.2.2
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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]

        Attachments

        1. maven-assembly.zip
          2 kB
          Adrian Stabiszewski

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              nitegate Adrian Stabiszewski
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: