Github user jlm429 commented on the issue:
https://github.com/apache/commons-cli/pull/14
Just adding this diff from the code above if needed for future reference.
this pr can be closed - do we possibly need more committers for CLI? It
doesn't seem like anyone is paying attenti
Github user jlm429 commented on the issue:
https://github.com/apache/commons-cli/pull/14
Just adding this diff from the code above if needed for future reference.
this pr can be closed - do we possibly need more committers for CLI? It
doesn't seem like anyone is paying attenti
Github user jlm429 commented on the issue:
https://github.com/apache/commons-cli/pull/14
fwiw - this is what I had to fix ... probably better off not digging around
in the default parser though if not needed :0
private void handleShortAndLongOption(String token) throws
Github user jlm429 commented on the issue:
https://github.com/apache/commons-cli/pull/14
fwiw - this is what I had to fix ... probably better off not digging around
in the default parser though if not needed :0
private void handleShortAndLongOption(String token) throws
Github user jlm429 commented on the issue:
https://github.com/apache/commons-cli/pull/14
Yep, that works for me.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user jlm429 commented on the issue:
https://github.com/apache/commons-cli/pull/14
Yep, that works for me.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user jlm429 commented on the issue:
https://github.com/apache/commons-cli/pull/14
my bad... I guess it makes sense to wait to merge the test until the bug is
fixed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user jlm429 commented on the issue:
https://github.com/apache/commons-cli/pull/14
my bad... I guess it makes sense to wait to merge the test until the bug is
fixed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user jlm429 opened a pull request:
https://github.com/apache/commons-cli/pull/14
Added BugCLI260 JUnit Test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jlm429/commons-cli master
Alternatively you can review and apply
