[
https://issues.apache.org/jira/browse/MJARSIGNER-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17794704#comment-17794704
]
ASF GitHub Bot commented on MJARSIGNER-63:
------------------------------------------
schedin commented on PR #14:
URL:
https://github.com/apache/maven-jarsigner-plugin/pull/14#issuecomment-1847147734
Even though `readonly` is not about documentation (primary), I feel that in
this context (for this specific case and JIRA tickets) it is about
documentation. In my comment in
https://issues.apache.org/jira/projects/MJARSIGNER/issues/MJARSIGNER-63 I have
provided a (rather long) example that shows that it is possible to set this
parameter, even if it is readonly (or undocumented).
My opinion is that we (the community) should make a conscious choice to make
sure that this parameter is configurable by the end-user (and also documented).
I think this was the original intent of
https://issues.apache.org/jira/projects/MJARSIGNER/issues/MJARSIGNER-53
> certchain should be supported by default
> ----------------------------------------
>
> Key: MJARSIGNER-63
> URL: https://issues.apache.org/jira/browse/MJARSIGNER-63
> Project: Maven Jar Signer Plugin
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Manfred Koch
> Priority: Major
>
> The certchain parameter of the jarsigne should be also supported by the Maven
> plugin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
