[
https://issues.apache.org/jira/browse/MAHOUT-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010875#comment-13010875
]
Sean Owen commented on MAHOUT-622:
----------------------------------
I think someone wanted to use features from Commons CLI 2.x, which is not (and
may never be) released. So there's a private copy.
AFAICT, 2.x was abandoned 7 years ago (http://commons.apache.org/cli/). I sorta
think we should not use it. That's a separate housecleaning issue, and a worthy
one (takers? is it really hard to undo?)
So I think you are welcome to do anything at all here that improves the
situation. If there's any official-er 2.x release, use that. It is supposed to
live in Commons Sandbox somewhere.
> 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
> Assignee: Dmitriy Lyubimov
> Priority: Minor
> Labels: build, maven, pom
> 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
