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

ASF GitHub Bot commented on FLUME-3183:
---------------------------------------

GitHub user szaboferee opened a pull request:

    https://github.com/apache/flume/pull/247

    FLUME-3183 Maven: generate SHA-512 checksum during deploy

    Addung SHA-512 checksum generation to maven
    Removed deprecated checksums
    Updated documentation

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/szaboferee/flume FLUME-3183

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flume/pull/247.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #247
    
----
commit b5eae26a3f9cbd90f9a37fcbd04ebe360cbd0a2e
Author: Ferenc Szabo <szaboferee@...>
Date:   2018-11-23T09:04:12Z

    FLUME-3183 Maven: generate SHA-512 checksum during deploy
    
    Addung SHA-512 checksum generation to maven
    Removed deprecated checksums
    Updated documentation

----


> Maven: generate SHA-512 checksum during deploy
> ----------------------------------------------
>
>                 Key: FLUME-3183
>                 URL: https://issues.apache.org/jira/browse/FLUME-3183
>             Project: Flume
>          Issue Type: Task
>    Affects Versions: 1.8.0
>            Reporter: Denes Arvay
>            Assignee: Ferenc Szabo
>            Priority: Minor
>             Fix For: 1.8.1, 1.9.0
>
>
> [~bessbd] wrote in the 1.8.0 RC2 vote email thread:
> _Please, note that I have only found .sha1 checksums, but as per 
> http://www.apache.org/dev/release-distribution#sigs-and-sums it is 
> recommended that "The checksum SHOULD be generated using SHA-512."_



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to