zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2915) Use "strict" conflict management in ivy
Date Sat, 07 Oct 2017 22:09:00 GMT

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

ASF GitHub Bot commented on ZOOKEEPER-2915:
-------------------------------------------

GitHub user afine opened a pull request:

    https://github.com/apache/zookeeper/pull/396

    ZOOKEEPER-2915: Use "strict" conflict management in ivy

    

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

    $ git pull https://github.com/afine/zookeeper ZOOKEEPER-2915_3.4

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

    https://github.com/apache/zookeeper/pull/396.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 #396
    
----
commit ea28ddc7ecc4eebe0fe1af2fb54dcabe578348c1
Author: Abraham Fine <afine@apache.org>
Date:   2017-10-06T21:43:05Z

    ZOOKEEPER-2915: Use "strict" conflict management in ivy

----


> Use "strict" conflict management in ivy
> ---------------------------------------
>
>                 Key: ZOOKEEPER-2915
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2915
>             Project: ZooKeeper
>          Issue Type: Improvement
>    Affects Versions: 3.5.4, 3.6.0, 3.4.11
>            Reporter: Abraham Fine
>            Assignee: Abraham Fine
>
> Currently it is very difficult to tell exactly which dependencies make it into the final
classpath of zookeeper. We do not perform any conflict resolution between the test and default
classpaths (this has resulted in strange behavior with the slf4j-log4j12 binding) and have
no way of telling if a change to the dependencies has altered the transitive dependencies
pulled down by the project. 
> Our dependency list is relatively small so we should use "strict" conflict management
(break the build when we try to pull two versions of the same dependency) so we can exercise
maximum control over the classpath. 
> Note: I also attempted to find a way to see if I could always prefer transitive dependencies
from the default configuration over those pulled by the test configuration (to make sure that
the zookeeper we test against has the same dependencies as the one we ship) but this appears
to be impossible (or at least incredibly difficult) with ivy. Any opinions here would be greatly
appreciated.



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

Mime
View raw message