[
https://issues.apache.org/jira/browse/HBASE-16369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-16369:
---------------------------------
Attachment: HBASE-16369.01.patch
Start with hbase-server, since that's where the trouble's been spotted. I've
seen dependency-plugin lie plenty of times about unused declared dependencies,
particularly regarding test runtime dependencies, so focus on used undeclared
for now.
> 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
> Fix For: 2.0.0
>
> 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.3.4#6332)
