Anton Koscejev

Hi everyone, here's a use-case we have for this issue and it also involves a JVM agent. We're building our production system as a docker container and then running tests...

One other example (besides annotations) is we have dependencies with `provided` scope, but unpack and process the contents via some custom build step, generating some code based on the contents,...

Perhaps they shouldn't. However, this is reality of the build we have right now and it works in maven with every other plugin and worked like this before for every...

We are experiencing the same issue. Cannot reproduce locally to debug properly, but it occurs quite reliably on our weaker build VMs. Could be some kind of race condition that...

Workaround: use `allowSetters = true` on the `@JsonIgnoreProperties` annotations.

- [x] Item 17 requirements should be item 4 + 98, not item 4 + 8. Edit from @Lurkars : should be fixed in [v0.67.9](https://github.com/Lurkars/gloomhavensecretariat/releases/tag/v0.67.9)

Encountered the same issue. Here's a workaround that uses a newer Gradle approach (.kts version): ```kotlin inputSpec = layout.buildDirectory.file("resources/main/openapi.yaml").map { it.asFile.toURI().toString() } ``` Note: this is using the processed resource...

I stumbled upon the same problem for reactive. Indeed, `FilePart` can be provided by Spring's `org.springframework.http.codec.multipart.DefaultPartHttpMessageReader`, but this reader actually implements `HttpMessageReader` and it provides `FilePart` only if the Content-Disposition...