public enum Toggle

A build hint the build server reads as true or false, plus the state of not having said either.

Not boolean, which cannot express the third state. boolean x() default false is read by anyone looking at it – and by IDE completion – as “off unless you turn it on”, which for many hints is simply untrue. It was harmless on the wire, because an attribute nobody writes is not written into the request either way, but it stated something about the build server that the client does not get to decide and cannot keep true.

So the third state is named instead of guessed. DEFAULT sends nothing and lets the server decide; ON and OFF are the developer overriding it.

Enum constants

`DEFAULT`	Say nothing, and let the build server apply its own default.
`ON`	Turn the hint on, whatever the server would otherwise have done.
`OFF`	Turn the hint off, whatever the server would otherwise have done.

Methods

`public static` `Toggle[] values()`
`public static` `Toggle valueOf(String name)`

Inherited methods

From Enum

clone, setEnumValues, getEnumValues, valueOf, equals, hashCode, toString, compareTo, name, ordinal, getDeclaringClass

From Object

getClass, notify, notifyAll, wait, wait, wait

Enum constant details

DEFAULT

DEFAULT

Say nothing, and let the build server apply its own default.

ON

ON

Turn the hint on, whatever the server would otherwise have done.

OFF

OFF

Turn the hint off, whatever the server would otherwise have done.

Method details

values

public static Toggle[] values()

valueOf

public static Toggle valueOf(String name)