[
https://issues.apache.org/jira/browse/COMMONSSITE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated COMMONSSITE-138:
---------------------------------------
Description:
I would like to have a {{signature-validator.sh}} at the root of the svn
distribution directory that accommodates validating all the signatures of the
release artifact. Maybe this goes here, maybe this should go in the individual
components?
For now I'm going to put it here for the sake of keeping things "DRY." I think
this file becomes complex for multi-module builds and we may want individual
projects to contribute their own signature-validator.sh file. I think
{{commons-rng}} will be a good place to show how to incorporate such a
customized file. (Happy to do the work myself)
was:
I would like to have a {{signature-validator.sh}} at the root of the svn
distribution director that accommodates validating all the signatures of the
release artifact. Maybe this goes here, maybe this should go in the individual
components?
For now I'm going to put it here for the sake of keeping things "DRY." I think
this file becomes complex for multi-module builds and we may want individual
projects to contribute their own signature-validator.sh file. I think
{{commons-rng}} will be a good place to show how to incorporate such a
customized file. (Happy to do the work myself)
> Create Signature Validation script for releases
> -----------------------------------------------
>
> Key: COMMONSSITE-138
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-138
> Project: Apache Commons All
> Issue Type: New Feature
> Components: Commons Release Plugin
> Affects Versions: 1.7
> Reporter: Rob Tompkins
> Assignee: Rob Tompkins
> Priority: Major
> Fix For: 1.8
>
>
> I would like to have a {{signature-validator.sh}} at the root of the svn
> distribution directory that accommodates validating all the signatures of the
> release artifact. Maybe this goes here, maybe this should go in the
> individual components?
> For now I'm going to put it here for the sake of keeping things "DRY." I
> think this file becomes complex for multi-module builds and we may want
> individual projects to contribute their own signature-validator.sh file. I
> think {{commons-rng}} will be a good place to show how to incorporate such a
> customized file. (Happy to do the work myself)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)