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

Hudson commented on MPOM-205:
-----------------------------

Build failed in Jenkins: Maven TLP » maven-apache-parent » master #35

See 
https://builds.apache.org/job/maven-box/job/maven-apache-parent/job/master/35/

> create SHA-256 and SHA-512 checksums in target/ during release
> --------------------------------------------------------------
>
>                 Key: MPOM-205
>                 URL: https://issues.apache.org/jira/browse/MPOM-205
>             Project: Maven POMs
>          Issue Type: New Feature
>          Components: asf
>    Affects Versions: ASF-20
>            Reporter: Hervé Boutemy
>            Priority: Major
>             Fix For: ASF-21
>
>
> currently, during Apache release, checksums are not created in target/ 
> directory: checksums are created on the fly during deploy to the Maven 
> repository
> while source release archive and its signature are available in target/, 
> checksums are not there: this gives people the bad habit to download 
> everything (not only checksums) from Apache Nexus repository after deploy to 
> copy to Apache /dist/
> it would be useful to have the checksums available in target/
> this would also prepare having new Apache checksums requirements for Apache 
> mirroring: http://www.apache.org/dev/release-distribution#sigs-and-sums
> sha256 and sha512 are not used for Maven repositories, but they are required 
> for Apache source release distribution



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to