[cli] Commons CLI
Hello, I've been using the Commons CLI library for various projects for several years now. The CLI library is nearly inactive, and I would to see that changed. The current version of CLI, 1.0, was released over two years ago. Since then, some work was done on a new 2.0 release, but that was never finished. The bug tracker is full of bugs relating to the 1.0 release, but there is no way to open new issues. Checking out the 1.0 branch, it apparently was branched some time after the 1.0 binary was created. Commons CLI is useful to many Java projects, and I think it's only going to become more visible once Commons is made a TLP. What I'd like to do: 1) Bug fix the 1.0 branch, and close some of the existing bug reports. 2) Get a 2.0 release, and re-open the/a bug tracking system. The 1.0 branch has enough features for most projects, and it's the release that nearly everyone uses, so I think it's worthwhile putting some maintenance effort into it. Since the bug tracker is closed for new bugs, and I can't find any active committers for this library, I haven't been able to contribute patches. Is there someone who has the time to help revive this project? I'm happy to do as much as a non-committer can do, but I need someone to help by reviewing and integrating patches updating the bug tracker, etc.. Cheers, Brian
Re: [cli] Commons CLI
I'm very happy to review and commit patches Brian - but I need someone to be doing the majority of the activity. The issue tracker for Commons moved, which is why you're finding that it's closed. http://issues.apache.org/jira/browse/CLI I've gone as far as to keep things generally in the right versions release wise. I also know there are others who would like to help with a release, but we're looking for someone to step up and drive the activity. So this is a great email to see :) Hen On 5/12/07, Brian A. Egge [EMAIL PROTECTED] wrote: Hello, I've been using the Commons CLI library for various projects for several years now. The CLI library is nearly inactive, and I would to see that changed. The current version of CLI, 1.0, was released over two years ago. Since then, some work was done on a new 2.0 release, but that was never finished. The bug tracker is full of bugs relating to the 1.0 release, but there is no way to open new issues. Checking out the 1.0 branch, it apparently was branched some time after the 1.0 binary was created. Commons CLI is useful to many Java projects, and I think it's only going to become more visible once Commons is made a TLP. What I'd like to do: 1) Bug fix the 1.0 branch, and close some of the existing bug reports. 2) Get a 2.0 release, and re-open the/a bug tracking system. The 1.0 branch has enough features for most projects, and it's the release that nearly everyone uses, so I think it's worthwhile putting some maintenance effort into it. Since the bug tracker is closed for new bugs, and I can't find any active committers for this library, I haven't been able to contribute patches. Is there someone who has the time to help revive this project? I'm happy to do as much as a non-committer can do, but I need someone to help by reviewing and integrating patches updating the bug tracker, etc.. Cheers, Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [CLI] commons-cli processing options incorrectly?
I've created a bugzilla entry and converted your example into a unit
test patch there: http://issues.apache.org/bugzilla/show_bug.cgi?id=30246
It definitely looks like a bug to me, but the obvious quick fix ended up
causing test failures elsewhere. I may come back to this and
investigate but it's more likely that I'll get CLI2 moving again and
ensure your example works against that.
Though I'm happy to apply fixing patches if people develop them.
Rob
Andrew Ferguson wrote:
-Original Message-
From: Andrew Ferguson [mailto:[EMAIL PROTECTED]
Sent: 15 July 2004 18:40
To: Jakarta Commons Users List
Subject: commons-cli processing options incorrectly?
hi,
this could be me misunderstanding the posix standard but this link
http://java.sun.com/docs/books/tutorial/essential/attributes/_posix.html
says
Options that do not require arguments can be grouped after a
hyphen, so, for example, -lst is equivalent to -t -l -s.
but the following code:
import org.apache.commons.cli.*;
import java.util.*;
public class CLITest {
public static void main(String[]arg) throws Exception {
CommandLineParser parser = new PosixParser();
Options options = new Options();
Option p = new Option(p, pets, true, takes
a list of up to 4 animals);
p.setArgs(4);
p.setRequired(true);
Option v = new Option(v, vet, true, the
name of a vet);
v.setArgs(100);
v.setRequired(true);
options.addOption(p).addOption(v);
CommandLine line = parser.parse(options, arg);
System.out.println(p ? +line.hasOption(p)+
+Arrays.asList(line.getOptionValues(p)));
System.out.println(v ? +line.hasOption(v)+
+Arrays.asList(line.getOptionValues(v)));
}
}
produces these results
y:\java\miscjava CLITest -p 1 2 3 -v 4 5 6
p ? true [1, 2, 3]
v ? true [4, 5, 6]
y:\java\miscjava CLITest -p 1 2 v 3 -v 4 5 6
p ? true [1, 2]
v ? true [4, 5, 6]
y:\java\miscjava CLITest -p 1 v 2 3 -v 4 5 6
p ? true [1]
v ? true [4, 5, 6]
y:\java\miscjava CLITest -p 1 V 2 3 -v 4 5 6
p ? true [1, V, 2, 3]
v ? true [4, 5, 6]
when I was expecting: (* marks different from above)
y:\java\miscjava CLITest -p 1 2 3 -v 4 5 6
p ? true [1, 2, 3]
v ? true [4, 5, 6]
y:\java\miscjava CLITest -p 1 2 v 3 -v 4 5 6
* p ? true [1, 2, v, 3]
v ? true [4, 5, 6]
y:\java\miscjava CLITest -p 1 v 2 3 -v 4 5 6
* p ? true [1, v, 2, 3]
v ? true [4, 5, 6]
y:\java\miscjava CLITest -p 1 V 2 3 -v 4 5 6
p ? true [1, V, 2, 3]
v ? true [4, 5, 6]
I'm constantly misunderstanding how command lines are meant to be
interpreted, but this seems wrong??
thanks,
Andrew
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
