[jira] [Commented] (MJARSIGNER-52) Cannot sign spring-boot 'fully executable' jar

["Marc Wrobel (JIRA)" <ji...@apache.org>]

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

Marc Wrobel commented on MJARSIGNER-52:
---------------------------------------

I think the issue comes from the usage of the JarSignerUtil#isZipFile() method in AbstractJarsignerMojo (see http://grepcode.com/file/repo1.maven.org/maven2/org.apache.maven.plugins/maven-jarsigner-plugin/1.4/org/apache/maven/plugins/jarsigner/AbstractJarsignerMojo.java#AbstractJarsignerMojo.isZipFile%28org.apache.maven.artifact.Artifact%29).

> Cannot sign spring-boot 'fully executable' jar
> ----------------------------------------------
>
>                 Key: MJARSIGNER-52
>                 URL: https://issues.apache.org/jira/browse/MJARSIGNER-52
>             Project: Maven Jar Signer Plugin
>          Issue Type: Bug
>    Affects Versions: 1.4
>         Environment: Linux, JDK 8
>            Reporter: Marc Wrobel
>            Priority: Minor
>
> When I try to sign a spring-boot 'fully executable' jar (e.g. jar file that embeds an extra script at the front of the file - see https://docs.spring.io/spring-boot/docs/current/reference/html/deployment-install.html) the maven-jarsigner-plugin ignores the artifact to sign :
> {quote}[INFO] --- maven-jarsigner-plugin:1.4:sign (sign) @ xxx ---
> [INFO] Unsupported artifact xxx ignored
> [INFO] 0 archive(s) processed{quote}
> If I sign the same artifact with JDK's jarsigner or if I sign a 'regular' jar everything is fine.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)