You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andreas Buchen (JIRA)" <ji...@apache.org> on 2017/11/10 19:37:00 UTC

[jira] [Commented] (MJARSIGNER-53) Add support of the certchain parameter to the "sign" mojo

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

Andreas Buchen commented on MJARSIGNER-53:
------------------------------------------

Hi,

Any plans to release the jarsigner plugin with the "certchain" argument?
I run into the same problem because my hardware token does not contain the full certificate chain and I need to provide the "certchain" argument. I can verify that the 1.5-SNAPSHOT build of 5 Nov works fine.

Andreas.

> Add support of the certchain parameter to the "sign" mojo
> ---------------------------------------------------------
>
>                 Key: MJARSIGNER-53
>                 URL: https://issues.apache.org/jira/browse/MJARSIGNER-53
>             Project: Maven Jar Signer Plugin
>          Issue Type: New Feature
>            Reporter: Oleg Nenashev
>            Assignee: Olivier Lamy (*$^¨%`£)
>              Labels: java7, options, signing
>             Fix For: 3.0.0
>
>
> "certchain" parameter has been added to jarsigner in Java SE 7. In my case it is required to do signing of JAR's with a hardware key (see [JENKINS-37567|https://issues.jenkins-ci.org/browse/JENKINS-37567]).
> I propose to add a new option to JAR Signer Lib and to Maven JarSigner Plugin. This option should be opt-in in order to keep the plugin compatible with the Java 6 flow



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