[ http://issues.apache.org/jira/browse/CLI-12?page=all ]
Hairong Kuang updated CLI-12: ----------------------------- Attachment: arg_pattern.patch here is the patch > [cli] Not handling property=value followed by 'remaining' args > -------------------------------------------------------------- > > Key: CLI-12 > URL: http://issues.apache.org/jira/browse/CLI-12 > Project: Commons CLI > Type: Bug > Environment: Operating System: other > Platform: Other > Reporter: Jim Skufca > Attachments: arg_pattern.patch > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]