.. and the next one:

released openapi-processor-spring/micronaut 2026.2

this release improves application/x-www-form-urlencoded handlig and 1xx/3xx response codes no longer complain about a missing success code.

See the release notes [2026.2](https://github.com/openapi-processor/openapi-processor-spring/releases/tag/v2026.2) for a description of the changes.

#openapiprocessor #openapi #springframework #micronaut

a bit late, but here we go:

released openapi-processor-spring/micronaut 2026.1

this release adds (marker) interface support for generated DTOs, target configuration for annotations and fixes duplicated `oneOf` interfaces.

See the release notes [2026.1](https://github.com/openapi-processor/openapi-processor-spring/releases/tag/v2026.1) for a description of the changes.

#openapiprocessor #openapi #springframework #micronaut

released openapi-processor-spring/micronaut 2025.5

this release adds OpenAPI 3.2 support and generation of unreferenced schemas.

See the release notes [2025.5](https://github.com/openapi-processor/openapi-processor-spring/releases/tag/v2025.5) for a description of the changes.

#openapiprocessor #openapi #springframework #micronaut

released openapi-processor-spring/micronaut 2025.4

It brings a few small improvements:

- use $ref filename without json pointer as class name
- check that bean validation annotations are allowed on the target type

See the release notes [2025.4](https://github.com/openapi-processor/openapi-processor-spring/releases/tag/v2025.4) for a description of the changes.

#openapiprocessor #openapi #springframework #micronaut

2/2

... to write

```gradle
sourceSets {
afterEvaluate {
main {
java {
// add generated files
srcDir(tasks.named("processSpring"))
}
}
}
}
```

and #gradle will know that it should run `processSpring` before `compileJava`. 😊

Unfortunately the `afterEvaluate` is needed because the task does not exist before `afterEvaluate`.

#openapiprocessor

2/2

1/2

With a rather small change to the #openapiprocessor #gradle plugin I was able to get rid of the ugly

```gradle
tasks.compileJava {
dependsOn("processSpring")
}
```

configuration. Instead of writing

```gradle
sourceSets {
main {
java {
// add generated files
srcDir("$projectDir/build/openapi")
}
}
}
```

it will be possible ...

...

released openapi-processor-spring/micronaut 2025.3

It brings two new features:

- generate interfaces and dtos with package-names based on file location
- generate response status annotations

See the release notes [2025.3](https://github.com/openapi-processor/openapi-processor-spring/releases/tag/v2025.3) for a description of the changes.

#openapiprocessor #openapi #springframework

released openapi-processor-spring/micronaut 2025.2

it improves response type handling and allows to drop parameters from the generated endpoint method.

See the release notes [2025.2](https://github.com/openapi-processor/openapi-processor-spring/releases/tag/v2025.2) for a description of the changes.

#openapiprocessor #openapi #springframework

.. the marker interface is simply

```java
package generated.model;

import generated.support.Generated;

@ Generated(value = "openapi-processor-core", version = "test")
public interface GetFooBarApplicationJsonResponse {
}
```

and the interface name is created from http method, path, contentType and “Response” to create a unique name.

2/2

#openapiprocessor #openapi

I have a prototype that automatically creates a marker interface for a response combination with different http status codes that return the same content type. For example: the an endpoints returns application/json on 200 & 202 with different content.

the endpoint then would look like

```java
@ Mapping("/fooBar")
GetFooBarApplicationJsonResponse getFooBarApplicationJson();
```

instead of

```java
@ Mapping("/fooBar")
Object getFooBarApplicationJson();
```

1/2

#openapiprocessor #openapi