You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Dmitriy Lyubimov (JIRA)" <ji...@apache.org> on 2015/06/18 21:09:20 UTC

[jira] [Commented] (MAHOUT-1277) Lose dependency on custom commons-cli

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

Dmitriy Lyubimov commented on MAHOUT-1277:
------------------------------------------

is this stale?

> Lose dependency on custom commons-cli
> -------------------------------------
>
>                 Key: MAHOUT-1277
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-1277
>             Project: Mahout
>          Issue Type: Improvement
>          Components: build, CLI
>    Affects Versions: 0.9
>            Reporter: Stevo Slavic
>            Assignee: Stevo Slavic
>            Priority: Minor
>              Labels: legacy, scala
>             Fix For: 0.11.0
>
>
> In 0.8 we have dependency on custom commons-cli fork org.apache.mahout.commons:commons-cli. There are no sources for this under Mahout version control. It's a risk keeping this as dependency.
> We should either use officially released and maintained commons-cli version, or if it's not sufficient for Mahout project needs, replace it completely with something else (e.g. like [JCommander|http://jcommander.org/]).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)