Mahout dependencies are unified under dependency management in parent pom
-------------------------------------------------------------------------
Key: MAHOUT-622
URL: https://issues.apache.org/jira/browse/MAHOUT-622
Project: Mahout
Issue Type: Improvement
Affects Versions: 0.4
Reporter: Dmitriy Lyubimov
Priority: Minor
Fix For: 0.5
As far as I understand, Maven encourages "best practice" of unified view of
dependency versions specified under <dependencyManagement> usually in a parent
pom, instead of under <dependencies>.
In Mahout, this practice is only partially followed. Some dependencies have
concrete versions under <dependencies> tag in submodule poms. Proposed change
is to raid those and move version declarations into parent pom.
This (as far as i understand) achieves 2 things:
* Mahout assembly would include same versions for all modules thus ensuring
runtime module dependencies are the same as compile time;
* Somebody who uses Mahout as a dependency, could import Mahout dependencies
using <scope>import</scope> spec thus inheriting Mahout's versions for shared
dependencies.
For most part the change would be nominal although in certain cases we'd need
to sort out through cross-module conflicts (if any). Commons-math was one, not
sure if there are more. If there are none, the changes would be rather
mechanistic.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
