[
https://issues.apache.org/jira/browse/CLI-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712857#action_12712857
]
Henri Yandell commented on CLI-168:
-----------------------------------
Realizing that I already moved it to the Sandbox back in March, so it's a
separate project already: http://commons.apache.org/sandbox/cli2/
The only overlap left is that they share the same JIRA project, which doesn't
seem too bad.
Yes it means that only Apache committers can work on it directly. That's a 50
fold increase on the number of people who could work on it in the released
components directory though (proper/).
I'd recommend mailing commons-dev@ to see if anyone is aiming to work on it and
can work with you via patches etc.
> Maven Repository Distribution as at least as -BETA may be as SNAPSHOT
> ---------------------------------------------------------------------
>
> Key: CLI-168
> URL: https://issues.apache.org/jira/browse/CLI-168
> Project: Commons CLI
> Issue Type: New Feature
> Components: CLI-2.x
> Environment: All
> Reporter: Karl Heinz Marbaise
> Fix For: 2.0
>
>
> It would be good to have at least a -BETA Releae of 2.0, so it could be used
> in Maven based builds. Otherwise it's complicated to use the
> commons-cli-2.0-DEV.
> It should be distributed via an Maven Repository to have access to the
> release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
