Default value of false for boolean does not work

[T3rm1]

Newest version: Result of my parsed arguments is {cache=mysql, duration=0, fillCache=false, writeRequestsPerSecond=0, readRequestsPerSecond=0, readThreadCount=5, size=4096, verbose=false, writeThreadCount=0}
Calling .isVerose() or isFillCache() returns true.

Cannot debug it because there are no sources for the .internal classes.

[lexicalscope]

I think perhaps the "isFillCache()" method could be telling you that
"fillCache" option is present rather than the value of its argument.

Perhaps what you are reporting is related to this previous issue report,
you may find the comments helpful:
#3 (comment)

If not, I am very busy this week, but I will try to look at this in more
detail next week if it is still a problem, sorry I can't respond any faster.

The .internal classes are copies of the dependencies with the package names
all changed (i.e. copies of guava and stuff). If you want to you can pull
the sources from github and open the project it eclipse and you should be
able to see all the source attachments and stuff.

(maven does the .internal renaming just before it creates the Jar for maven
central).

On Wed, Mar 26, 2014 at 1:04 PM, T3rm1 notifications@github.com wrote:

Newest version: Result of my parsed arguments is {cache=mysql, duration=0,
fillCache=false, writeRequestsPerSecond=0, readRequestsPerSecond=0,
readThreadCount=5, size=4096, verbose=false, writeThreadCount=0}
Calling .isVerose() or isFillCache() returns true.

Cannot debug it because there are no sources for the .internal classes.

Reply to this email directly or view it on GitHubhttps://github.com//issues/31
.

[T3rm1]

getVerbose() or getFillCache() returns true as well. It's a bug in the code. If I remove the defaultValue attribute from the annotation it works. I know that it makes no sense to specify the defaultValue attribute but if you accidently do it then the code doesn't work.

[jasonCodesAway]

I'm also seeing this behavior in version 0.8.9. FWIW here is the code that returns true, regardless of what I set 'defaultValue' to:

@Option(shortName = "nu", longName = "no-ui", defaultValue = "false")
boolean suppressUi();

[joshuabambrick]

As per #3 I believe that this is the intended implementation. I would be inclined to agree that supporting boolean arguments that default to false would be useful, but it is not a bug.

The linked issue offers a work-around.