You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Mike Drob (JIRA)" <ji...@apache.org> on 2017/10/26 18:12:00 UTC
[jira] [Resolved] (HBASE-16369) Clean up dependency management
[ https://issues.apache.org/jira/browse/HBASE-16369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Drob resolved HBASE-16369.
-------------------------------
Resolution: Duplicate
Fix Version/s: (was: 2.0.0)
This happened sometime around 2.0-alpha2
> Clean up dependency management
> ------------------------------
>
> Key: HBASE-16369
> URL: https://issues.apache.org/jira/browse/HBASE-16369
> Project: HBase
> Issue Type: Task
> Components: build
> Reporter: Nick Dimiduk
> Priority: Critical
> Labels: beginner
> Attachments: HBASE-16369.00.patch, HBASE-16369.01.patch
>
>
> Following the test breakage of HBASE-16317, and related issues HBASE-16361, and HBASE-15767, it's clear we don't have a handle on our dependencies. Not only does it lead to unexpected errors from used, undeclared dependencies, it also means we're at something of a loss to guarantee our dependencies in light of our compatibility guidelines. Adopt use of some combination of the [dependency|http://maven.apache.org/plugins/maven-dependency-plugin/usage.html] and [enforcer|http://maven.apache.org/enforcer/enforcer-rules/banTransitiveDependencies.html] plugins to assist in accounting.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)