commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russel Winder (JIRA)" <>
Subject [jira] Commented: (CLI-143) Put CLI 2.x into Maven repository
Date Wed, 15 Aug 2007 06:01:30 GMT


Russel Winder commented on CLI-143:

Thanks for acting on this one so quickly, it is much appreciated.  I can now get on with experiments
as it is not required to checkout the CLI source and build the jar myself.  Actually I have
done this, but the problem is that others on the Groovy team would not want to.

One issue though.  Shouldn't the name be:


or perhaps this is really:


I am not sure Maven is actually happy with jars with no version number.

A second issue I just spotted.  This is the Maven 1 repository.  I think in general people
consider Maven 1 anathema and use only Maven 2.  Is there an auto move from the Maven 1 to
the Maven 2 repository or should the Maven 2 POM be used to publish into the Maven 2 repository.

I guess this raises the issue as to whether it is sensible to have three parallel build systems:
 Ant, Maven 1, and Maven 2, or whether to restrict this just to one.  Maven 2 would be my


> Put CLI 2.x into Maven repository
> ---------------------------------
>                 Key: CLI-143
>                 URL:
>             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.

View raw message