You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Attila Simon (JIRA)" <ji...@apache.org> on 2017/07/20 10:56:00 UTC

[jira] [Comment Edited] (FLUME-3134) Enforce version of library dependencies during mvn build

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

Attila Simon edited comment on FLUME-3134 at 7/20/17 10:55 AM:
---------------------------------------------------------------

The idea came from a discussion on the dev@ list between [~ralph.goers@dslextreme.com] and [~mpercy]:


{quote}
> Mike,
>
> In all the projects I actively work on I put a dependencyManagement
> section in the parent pom and try to specify the version of every
> dependency there, whether direct or transitive. I also add the Maven
> enforcer plugin to make sure that subproject aren’t specifying differing
> versions of the same dependency.
>
> If one of the dependencies uses a library that is incompatible with a
> later version then you should create a bug report for that dependency so
> they can get it fixed.
>
> Ralph
>

Hey Ralph,
Nice. I didn't know enforcer could do that. After looking at its usage page
it seems easy to set up, too:
http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html

I would definitely be +1 for harmonizing Flume's dependencies and adding a
dependencyConvergence check to the Maven build. That first step should be
done with some care, though.

Mike
{quote}




was (Author: sati):
The idea came from a discussion on the dev@ list:

{noformat}
> Mike,
>
> In all the projects I actively work on I put a dependencyManagement
> section in the parent pom and try to specify the version of every
> dependency there, whether direct or transitive. I also add the Maven
> enforcer plugin to make sure that subproject aren’t specifying differing
> versions of the same dependency.
>
> If one of the dependencies uses a library that is incompatible with a
> later version then you should create a bug report for that dependency so
> they can get it fixed.
>
> Ralph
>

Hey Ralph,
Nice. I didn't know enforcer could do that. After looking at its usage page
it seems easy to set up, too:
http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html

I would definitely be +1 for harmonizing Flume's dependencies and adding a
dependencyConvergence check to the Maven build. That first step should be
done with some care, though.

Mike
{noformat}


> Enforce version of library dependencies during mvn build
> --------------------------------------------------------
>
>                 Key: FLUME-3134
>                 URL: https://issues.apache.org/jira/browse/FLUME-3134
>             Project: Flume
>          Issue Type: Bug
>    Affects Versions: 1.7.0
>            Reporter: Attila Simon
>              Labels: dependency
>
> http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)