[
https://issues.apache.org/jira/browse/CLI-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520009
]
Henri Yandell commented on CLI-143:
-----------------------------------
Maven should be happy. It is a bit weird though to have SNAPSHOT and not
2.0-SNAPSHOT in maven2 nowadays. It's a legacy of our shell script build system.
As we're moving away from that to Continuum currently, I think it's best to
leave it be and let the general move improve that. Unless of course SNAPSHOT as
a version causes errors.
You can use m1 repositories from maven2, do a <layout>legacy</layout> within
the <repository> element.
Generally Commons components are Maven1 builds, with Ant available for those
who don't like Maven. A few components are Ant builds due to painful issues
that made Maven hard to setup fully. The move is now underway to move to Maven2
as the default build; at which point I'm definitely +1 to delete the Maven1
builds.
> Put CLI 2.x into Maven repository
> ---------------------------------
>
> Key: CLI-143
> URL: https://issues.apache.org/jira/browse/CLI-143
> Project: Commons CLI
> Issue Type: Bug
> Components: CLI-2.x
> Affects Versions: 2.0, 2.1
> Reporter: Russel Winder
> Priority: Critical
>
> The groundswell appears to lead to CLI 1.x being declared at End Of Life and
> for CLI 2.x to become the new main stream. However, there is no version of
> CLI 2.x in the Maven repository. I think a SNAPSHOT release of some version
> of the 2.x branch should be put out as a matter of urgency.
> (This will enable me to try 2.x out with Groovy and report back.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
