• JACKSON2 (apply annotations from the Jackson 2.x library)
• JACKSON (alias for JACKSON2)
• JSONB (apply annotations from the JSON-B 1.x library)
• JSONB2 (apply annotations from the JSON-B 2.x library)
• GSON (apply annotations from the Gson library)
• MOSHI1 (apply annotations from the Moshi 1.x library)
• NONE (apply no annotations at all)

• ALWAYS Value that indicates that property is to be always included, independent of value of the property.
• NON_ABSENT Value that indicates that properties are included unless their value is: null "absent" value of a referential type (like Java 8 `Optional`, or {link java.utl.concurrent.atomic.AtomicReference}); that is, something that would not deference to a non-null value.
• NON_DEFAULT Meaning of this setting depends on context: whether annotation is specified for POJO type (class), or not.
• NON_EMPTY Value that indicates that only properties with null value, or what is considered empty, are not to be included.
• NON_NULL Value that indicates that only properties with non-null values are to be included.
• USE_DEFAULTS Pseudo-value used to indicate that the higher-level defaults make sense, to avoid overriding inclusion value.

If a support for filesets/filelists/dirsets etc is required, this property can also be set as a nested element like:

<jsonschema2pojo ...
    <classpath>
        <fileset dir="custom-libs">
            <include name="**/*.jar" />
        </fileset>
    </classpath>
<jsonschema2pojo/>

A fully qualified class name, referring to a custom annotator class that implements org.jsonschema2pojo.Annotator and will be used in addition to the one chosen by annotationStyle.

If you want to use the custom annotator alone, set annotationStyle to none.

A fully qualified class name, referring to a custom rule factory class that extends org.jsonschema2pojo.rules.RuleFactory.

By specifying a custom implementation you can customize most aspects of code generation by returning custom instances of rules.

Whether to include json type information; often required to support polymorphic type handling.

By default the type information is stored in the @class property, this can be overridden in the deserializationClassProperty of the schema.

Schema rules and the annotation they produce:

• maximum = @DecimalMax
• minimum = @DecimalMin
• minItems,maxItems = @Size
• minLength,maxLength = @Size
• pattern = @Pattern
• required = @NotNull

Schema rules and the annotation they produce:

• required = @NonNull

Be warned, when activated this option will cause jsonschema2pojo to indiscriminately delete the entire contents of the target directory (all files and folders) before it begins generating sources.

Supported values:

• JSONSCHEMA (schema documents, containing formal rules that describe the structure of JSON data)
• JSON (documents that represent an example of the kind of JSON data that the generated Java types will be mapped to)
• YAMLSCHEMA (JSON schema documents, represented as YAML)
• YAML (documents that represent an example of the kind of YAML (or JSON) data that the generated Java types will be mapped to)

• org.joda.time.LocalDateTime (Joda)
• java.time.LocalDateTime (JSR310)

• org.joda.time.LocalDate (Joda)
• java.time.LocalDate (JSR310)

• org.joda.time.LocalTime (Joda)
• java.time.LocalTime (JSR310)

• OS (Let the OS influence the order that the source files are processed.)
• FILES_FIRST (Case sensitive sort, visit the files first. The source files are processed in a breadth first sort order.)
• SUBDIRS_FIRST (Case sensitive sort, visit the sub-directories before the files. The source files are processed in a depth first sort order.)