new constructor for CmdLineParser to optionally not sort options. This is because the order of the options might be purposeful, for example grouping them logically.

@Option(name="-u",required=true,aliases="--username",usage="Username for login")
private String username;
@Option(name="-g",forbids={"-u"},aliases="--generate",usage="generate random key")
private boolean generate;

When i use this option i get this two errors:

Options.java:24: error: cannot find symbol
@Option(name="-g",forbids={"-u"},aliases="--generate",usage="generate random key")
                  ^
symbol:   method forbids()
location: @interface Option
Options.java:24: error: illegal initializer for <none>
@Option(name="-g",forbids={"-u"},aliases="--generate",usage="generate random key")
                          ^
2 errors

Hi,

This is Mingtao. It's my first attempt in open source ... Seems unit-test and integration-test both passed.

Target on fixing the above scenario. Specifically for -h, which let -h possibly forbids other options.

I really have trouble to remove several files that I don't want to commit ... .classpath .gitignore bin/META-INF/services/com.sun.mirror.apt.AnnotationProcessorFactory and those *.class files.

For a project of mine I needed to parse MAC addresses. Mostly, MAC addresses are represented by a byte array of length 6 in Java. The string representation of a MAC address can be of different forms, e.g.

XXXXXXXXXXXX XX XX XX XX XX XX XX-XX-XX-XX-XX-XX XX:XX:XX:XX:XX:XX

where X is a hexadecimal digit. I used an abstract delimiter (name it #) with the only constraint that # does not contain any hexadecimal digit. As an alternative, one can enter a string with 12 letters only containing hexadecimal digits.

You may want to merge my code to Your project. If You need more help (e.g. because I forgot something or made something wrong) please ask.

Right now usage displays options in a form like "--key value". Want the option to show "--key=value". This is determined by a setting in CmdLineParser, "useEqualsforOptionUsage"

Some minor code cleanups

• compression of null pointer checks in JDK 1.6 compatible way
• some small JavaDoc for a newly added interface
• smaller cleanups

I commonly use Args4J annotations on my "set argument" methods. For example:

@Option(name = "-numdays", usage = "number of days up to and including lastdate to process", required = false)
public void setNumDays(int numDays) {
    _numDays = numDays;
}

I'd like to use the multiValued=true qualifier in the same manner, but although the following compiles...

@Option(name = "-importdir", usage = "directory containing crawl info to import", required = true, multiValued = true)
public void setImportDirs(List<String> importDirs) {
    _importDirs = importDirs;
}

...I get an error at runtime when I try to specify this argument multiple times (e.g., "-importdir dir1 -importdir dir2"):

org.kohsuke.args4j.IllegalAnnotationError: No OptionHandler is registered to handle interface java.util.List

I note that MultivaluedTest applies the annotation to the instance variable directly. Is this the only way to make use of the multiValued qualifier, or have I made some other egregious error in my implementation?

The MapSetter class now correctly deals with multiple '=' signs being present in the value part. This changes the behaviour as follows:

Input: "foo=bar=baz" Old (key, value): ("foo", "bar") New (key, value): ("foo", "bar=baz")

Converted mixed indentation to only-tabs. Added copyright statement and MIT licence text.

Fixes: https://github.com/kohsuke/args4j/issues/12 Signed-off-by: Martin Schroeder [email protected]

... for better readability.

Fixes #54

New Output:

"xy" is not a valid value for "-e"
 -e (--environment) training, productio : application environment (default:
 n, testing, development, custom          development)

Hi Kohsuke,

Args4j should definitely have the following feature (which present in JCommander): support for args in format -argname=argvalue

I change a little CmdLineParser.java and added some unit tests to give examples

I am very interested in contributing to your project, this is the first contribution I have worked on, and while it may be a small one, it will also make a world of difference for people as they move to java 7 and nio2. Please give me any feedback, I am willing to make changes or additional work on this, and hope to provide many contributions in the future.

Thanks, -Kevin-

Resolves #131

I'm working on a large enterprise application codebase, which allows creation of multiple different application entry points for the same codebase. Many of these applications share base command line parameters, but different apps have different required fields vs optional fields. There are a large number of command line arguments, so it would be useful in our particular case to be able to override them. This PR adds the ability to use a different version of ClassParser, and provides a new ClassParser subclass which allows subclasses to override arg4j annotations on parent methods/fields.

Hey I noticed this broken link on http://args4j.kohsuke.org/ and that you had fixed it in the README by pointing to the wayback machine. Guessing that the site is statically generated, here's an update to the links

Hi, when using this project as a dependecy in another project it tells me that tools.jar cannot be found. [ERROR] Failed to execute goal on project ***: Could not resolve dependencies for project com.***.plugins:commit-pipeline-xml:hpi:0.1: Could not find artifact jdk:tools:jar:5.0 at specified path /usr/local/java/jdk-14.0.2/../lib/tools.jar -> [Help 1]

Is there a solution to this?

Replace the non-standard NotImplementedException with UnsupportedOperationException.

At Google, we are upgrading our standard JVM and will no longer have access to sun.reflect.generics.reflectiveObjects.NotImplementedException. This ensures we will be able to run the tests in the future.

Could it be a good addition to be able to also parse environment variables?

For example, you could have a program in which you could specify the host to connect to with a --host 127.0.0.1 or with an environment variable "HOST" with the value "127.0.0.1". This could help when it used in places where they commonly use environment variables like in Helm / Kubernetes.

Nowadays, if you want this behavior you should implement both separately so you can have a problem of not synchronizing it when they change and duplicate validation code, etc.

Could it be a good idea?