Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of jukka.zitting@gmail.com
 designates 209.85.218.224 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:from:date:message-id:subject:to:content-type;
        b=Awoq8G7KbfCHlsGGkEgWmVkjWxK9uM+4b8V1/Qh8oweOSXe0Va6078GYzhCYqI3QeB
         gvtOOzFwuHylO0pmPoCODCfG2MQoibgfndci8uqRaKfEBBmFBtPh9YJN0Gb6EiznphfO
         3yTXdDsyM3xjj5gKswv9eGib9JAkEm8nvKONI=
MIME-Version: 1.0
From: Jukka Zitting <jukka.zitting@gmail.com>
Date: Wed, 11 Nov 2009 22:14:30 +0200
Message-ID: <510143ac0911111214m1a30a5c0h3d06df6073dfa1f7@mail.gmail.com>
Subject: [cli] (or [cli2]?) Plans for CLI 2.0 release?
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Apache Mahout is moving to fully a Maven-based build/release process
and they're having problems with the commons-cli 2.0 dependency which
I believe they get through Hadoop. To solve the dependency issue,
Mahout has deployed that snapshot to Maven central as
org.apache.mahout.commons:commons-cli:2.0-mahout. This works for now,
but is clearly not an ideal solution.

So, are there plans for releasing CLI 2.0? The codebase is obviously
already being used, so having an official release would be quite nice.
If the API is still not final, would it make sense to release
something like 2.0-alpha1 to make downstream projects happy without
making strict backwards compatibility commitments?

BR,

Jukka Zitting

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org