[CLI-12] [cli] Not handling property=value followed by 'remaining' args

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0
• Fix Version/s: 2.0
• Component/s: CLI-2.x

Environment

Operating System: other
Platform: Other

• Bugzilla Id: 34228
• Assignee: Unassigned
• Reporter: Jim Skufca
• Created: 30/Mar/05 06:16
• Updated: 15/Mar/07 16:49
• Resolved: 12/Jul/06 13:04

Description

If you have a command line args similar to

domything -Dmyprop1=myval1 -Dmyprop2=myval2 myfile

I would expect to be able to set up the 'D' option so that

String[] opts = line.getOptionValues( "D" );
assertEquals( "myprop1", opts[0] );
assertEquals( "myval1", opts[1] );
assertEquals( "myprop2", opts[2] );
assertEquals( "myval2", opts[3] );

String[] xtraArgs = line.getArgs();
assertEquals( "myfile", xtraArgs[0]);

But, setting up similar to the ApplicationTest.java I get 'myfile' as opts
[4]. Since we have set up the 'D' option with hasArgs, it will only stop
adding args to 'D' when it runs into another valid option, not an extra arg.
If you set up the 'D' option with hasArg (singular) then it myprop1=myval1
gets reported as an invalid option.

I've glanced at the source but didn't see an obvious fix that wouldn't
jeopardize the combinations and permutations that Option.addValue() must deal
with.