Fiete

It seems that the necessary .aux files are being created in ~/.cache/gummi/. To temporarily fix the issue, you can create a "subdir" Folder in ~/.cache/gummi/.

Any progress on this? It looks like this causes test runs to fail in VSCode (see [vscode-java-test - The property file in src/test/resources is not recognized and the test fails](https://github.com/microsoft/vscode-java-test/issues/1311))

> Root cause is that the upstream does not specially put the test output location before the main output location. > > Same bug can be seen in Eclipse as...

Oh thanks, I didn't know about that yet! For my use case, I have now defined the following snippet: ``` json "Code block": { "prefix": ["cbb"], "body": [ "``` bash",...

I have solved the problem by customizing the `formParams.mustache` template to revert the change. For that, I have copied the file [from the repo](https://github.com/OpenAPITools/openapi-generator/blob/6.1.x/modules/openapi-generator/src/main/resources/JavaSpring/formParams.mustache) (make sure to use the appropriate...

Thanks for the suggestion @snjeza this does help, but is applied to the whole project. It kind of misses the point of ignoring problems for some subfolders though...

@rgrunber I am not sure I fully understand what you are suggesting. Are you saying I should add `@SuppressWarnings("all")` to every generated java class? That would unfortunately be not possible...

Apologies if I am missing your point and at the risk of repeating myself: In our setup the source files (i.e the restcontrollers) are completely transient, they are not versioned...

I just took a look on the openapi-generator issue tracker and found [this related feature request](https://github.com/OpenAPITools/openapi-generator/issues/9752) to add `@SuppressWarnings` to the generated code. Maybe that would tackle the problem more...

~~The import does not seem to be correctly added for the `jersey` and `feign` clients. I still need to investigate, but my first guess is that they are maybe not...