Henri Yandell wrote:
CLI 2.0 I don't see any time soon (ever) unless someone gets a big urge.
CLI 1.2 I have on my list as a 'sometime soon' along with the next
Collections 3.x and Codec 1.x - looking at it I think it could go very
easily, none of the 4 tickets are blocked (ignoring that CLI-137 is a
painful one to close as WONTFIX).
[...]
I have done some work on CLI-137 as part of the Debian packaging. I
think it is quite a severe bug, as it does not allow you to handle (for
example) multiple "-D" arguments (as found in Maven or ant).
I've prepared a patch for it for the Debian build (although I do not
necessarily think that's the best way to fix it), and amended the JUnit
tests to demonstrate the problem.
I sent an email to the -dev list a few weeks ago, but I think it might
have gone missing. Here it is:
Hi,
I've fallen over the CLI bug described in issue 137, and I'm wondering
if I can help provide a patch for it? I'd appreciate someone just
checking my logic in case I'm missing something obvious. I'm using
release 1.1, by the way.
As far as I can see it is simply not possible to use commons-cli to
parse repeating options, such as occur in ant:
ant -Dproperty1=value1 -Dproperty2=value2 compile
Cli *does* have a junit test for ant-type options, but it unfortunately
doesn't catch the error because it tests the command line:
ant -Dproperty1=value1 -Dproperty2=value2 -projecthelp
I attach a patch for the junit test (Cli-junit.patch) that will provoke
the error, if you want to try it yourself.
_Here's what I think is happening:_
The unit test (and the work-around suggested in issue 137) creates the
"D" option using "hasArgs()" [note the 's' on the end of the method
name]. Using hasArgs() for the "D" option causes cli to assume that all
arguments following the "-D" (until it encounters another option) belong
to the "-D" option. I've probably not explained that clearly so here's
an example:
ant -Dproperty1=value1 -Dproperty2=value2 compile
will treat "compile" as though it was "-Dcompile". getArgs() will return
0 elements, rather than one ("compile").
If instead you construct the "D" option using hasArg() [singular] then
it will *not* interpret the second "-D" as an option. getArgs() will
return 2 elements: "property2=value2" and "compile". getOptionValues()
will return only the first -D value.
This problem first came to light when Debian upgraded CLI from 1.0 to
1.1, and caused Debian's Maven package to fail (the standard Maven
package uses cli 1.0 of course). As part of the Debian packaging I have
created a quick-and-dirty patch which allows Maven to work (see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469082 for the Debian
bug report, and I have attached the patch (MultiOptions.patch). I would
guess that a proper fix would be rather more elegant than my patch.
Thanks,
Paul Cager
Index: src/test/org/apache/commons/cli/ApplicationTest.java
===================================================================
--- src/test/org/apache/commons/cli/ApplicationTest.java (revision
635884)
+++ src/test/org/apache/commons/cli/ApplicationTest.java (working copy)
@@ -96,15 +96,16 @@
options.addOption( "listener", true, "add an instance of a class as a
project listener" );
options.addOption( "buildfile", true, "use given buildfile" );
options.addOption( OptionBuilder.withDescription( "use value for given
property" )
- .hasArgs()
+ .hasArgs(1)
.withValueSeparator()
.create( 'D' ) );
//, null, true, , false, true );
options.addOption( "find", true, "search for buildfile towards the
root of the filesystem and use it" );
String[] args = new String[]{ "-buildfile", "mybuild.xml",
+ "-projecthelp",
"-Dproperty=value", "-Dproperty1=value1",
- "-projecthelp" };
+ "compile" };
try {
CommandLine line = parser.parse( options, args );
@@ -121,6 +122,7 @@
// check option
assertTrue( line.hasOption( "projecthelp") );
+ assertEquals(1, line.getArgs().length);
}
catch( ParseException exp ) {
fail( "Unexpected exception:" + exp.getMessage() );
@@ -128,4 +130,4 @@
}
-}
\ No newline at end of file
+}
Index: src/java/org/apache/commons/cli/Option.java
===================================================================
--- src/java/org/apache/commons/cli/Option.java (revision 635884)
+++ src/java/org/apache/commons/cli/Option.java (working copy)
@@ -437,13 +437,15 @@
// while there are more value separators
while (index != -1)
{
- // next value to be added
- if (values.size() == (numberOfArgs - 1))
- {
- break;
- }
+ // Next few lines commented out in the patch. You
+ // can have multiple values in one argument, so it does not
+ // make sense to terminate the loop early (you would lose
+ // the excess arguments anyway).
+// if (values.size() == (numberOfArgs - 1))
+// {
+// break;
+// }
-
// store
add(value.substring(0, index));
@@ -463,9 +465,7 @@
}
/**
- * Add the value to this Option. If the number of arguments
- * is greater than zero and there is enough space in the list then
- * add the value. Otherwise, throw a runtime exception.
+ * Add the value to this Option.
*
* @param value The value to be added to this Option
*
@@ -473,10 +473,14 @@
*/
private void add(String value)
{
- if ((numberOfArgs > 0) && (values.size() > (numberOfArgs - 1)))
- {
- throw new RuntimeException("Cannot add value, list full.");
- }
+ // The patch removes the following code as we check for
+ // numberOfArgs in the caller (where we can tell the difference
+ // between (e.g) multiple instances of an option versus one
+ // instance of the option with multiple arguments).
+// if ((numberOfArgs > 0) && (values.size() > (numberOfArgs - 1)))
+// {
+// throw new RuntimeException("Cannot add value, list full.");
+// }
// store value
Index: src/java/org/apache/commons/cli/Parser.java
===================================================================
--- src/java/org/apache/commons/cli/Parser.java (revision 635884)
+++ src/java/org/apache/commons/cli/Parser.java (working copy)
@@ -325,7 +325,9 @@
public void processArgs(Option opt, ListIterator iter)
throws ParseException
{
- // loop until an option is found
+ // loop until another option is found, or we have read the maximum
+ // number of args.
+ int argCount = 0;
while (iter.hasNext())
{
String str = (String) iter.next();
@@ -347,6 +349,12 @@
iter.previous();
break;
}
+
+ argCount++;
+ if (argCount >= opt.getArgs() && opt.getArgs() >= 0)
+ {
+ break;
+ }
}
if ((opt.getValues() == null) && !opt.hasOptionalArg())
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
