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

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

GitHub user mcsanady opened a pull request:

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

    FLUME-3093: Groundwork for version changes in root pom

    Extracted hard-coded version numbers to root pom.xml
    
    No version number changed in this step. The old used versions are named 
with -old suffix.
     guava-old.version
     httpclient-old.version
     mvn-surefire-plugin-old.version
     mvn-surefire-plugin-old-morphline.version

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

    $ git pull https://github.com/mcsanady/flume FLUME-3093

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

    https://github.com/apache/flume/pull/132.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 #132
    
----
commit a7239a96b144aa4299c5381cb8c97d35fa57822c
Author: Miklos Csanady <miklos.csan...@cloudera.com>
Date:   2017-05-17T06:52:09Z

    FLUME-3093: Groundwork for version changes in root pom
    
    Extracted hard-coded version numbers to root pom.xml
    
    No version number changed in this step. The old used versions are named 
with -old suffix.
     guava-old.version
     httpclient-old.version
     mvn-surefire-plugin-old.version
     mvn-surefire-plugin-old-morphline.version

----


> Groundwork for version changes in root pom
> ------------------------------------------
>
>                 Key: FLUME-3093
>                 URL: https://issues.apache.org/jira/browse/FLUME-3093
>             Project: Flume
>          Issue Type: Task
>    Affects Versions: 1.7.0
>            Reporter: Miklos Csanady
>
> Flume's root pom should have a parameter block where all the dependency 
> versions are listed. 
> This is fundamental to later version changes required to time effectively 
> overcame 3rd party security vulnerabilities.
> This should be done in two steps: first just refactoring with no change, the 
> second is getting rid of unnecessary different versions.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to