maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MASSEMBLY-593) jarsigner plugin failes after assembly plugin
Date Sat, 14 May 2016 23:33:12 GMT

    [ https://issues.apache.org/jira/browse/MASSEMBLY-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15283723#comment-15283723
] 

Michael Osipov commented on MASSEMBLY-593:
------------------------------------------

Still happens but works with {{mvn clean package -Djarsigner.processMainArtifact=false}}.

> 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
>         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.3.4#6332)

Mime
View raw message