Release 1.2.0 · openapi-processor/openapi-processor-base

add @NotNull if nullable is default (i.e. true) and bean validation is enabled.
openapi-processor/openapi-processor-core#20, the type mapping (v2 only) configuration allows to reference the target package-name in generic parameters using the {package-name} expression. This makes it possible to adjust the package-name without touching the mapping and it can reduce duplication if the mapping contains many generic parameters.
```
openapi-processor-mapping: v2
options:
  package-name: io.openapiprocessor.generated.model

map:
  types:
    - type: FooPage => org.springframework.data.domain.Page<{package-name}.Foo>
```
openapi-processor/openapi-processor-core#21, a primitive type with a custom format (not defined by the OpenAPI specification) did break processing. The processor does now ignore unknown custom formats. For example the following definition
```
type: string
format: unknown-custom-format
```
will be processed as if it has no format at all:
```
type: string
```
openapi-processor/openapi-processor-core#22, mapping of primitive schemas did not work. It is now possible to have a primitive schema
```
components:
  schemas:
    Foo:
      type: string
```
and map this to a specific target java type:
```
openapi-processor-spring: v2

map:
  types:
    - type: Foo => io.openapiprocessor.sample.Foo
```
openapi-processor/openapi-processor-core#23, parameter $ref's were not resolved when processing with the openapi4j parser.
updated openapi4j parser to 1.0.4 (was 1.0.3)

Provide feedback