You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lasse Lindqvist (JIRA)" <ji...@apache.org> on 2018/12/19 19:36:00 UTC
[jira] [Commented] (MJARSIGNER-52) Cannot sign spring-boot 'fully
executable' jar
[ https://issues.apache.org/jira/browse/MJARSIGNER-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725305#comment-16725305 ]
Lasse Lindqvist commented on MJARSIGNER-52:
-------------------------------------------
I don't see that the plugin should support signing the executable. Jarsigner can be run before spring-boot-maven-plugin is run with repackage goal. This can be achieved with lifecycle configuration or plugin ordering.
> 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
(v7.6.3#76005)