jimshowalter

"Maybe you can test with current versions". I'm already doing that. See the above list. Everything is on the latest. That's why I'm saying, the only thing that's change is...

Correct.

The way our codegen tests work is we have the above dependencies, and we run the ben-manes dependency analyzer (in every build) to see if there's anything new. If so,...

I'm trying to create a cut-down version of one of our schemas that shows the problem.

Haven't been able to cut down the schema yet, but here's one of the symptoms: Exception in thread "Thread-5" java.lang.StackOverflowError at io.swagger.v3.oas.models.media.Schema.toString(Schema.java) at io.swagger.v3.oas.models.media.StringSchema.toString(StringSchema.java:84) at java.lang.String.valueOf(String.java:2994) at java.lang.StringBuilder.append(StringBuilder.java:131) at java.util.AbstractMap.toString(AbstractMap.java:559)...

Yes, that's fine. Working on the spec. Looking at your branch, it appears that after ignoring tests, the schema, and changes to code that only affect formatting, there is only...

This shows the infinite recurse: [example0.zip](https://github.com/swagger-api/swagger-parser/files/6469786/example0.zip)

I'll work on examples of the other problems tomorrow.

This one outputs: public Error setBad(List\ bad) { but it should output: public Error setBad(List\ bad) { Note that config.json specifies a modelName. [example1.zip](https://github.com/swagger-api/swagger-parser/files/6474186/example1.zip)

When the swagger-parser is called from swagger-cli's SwaggerCodegen, the messages are logged but the code generator fails silently. The only way to get the messages is to fork the code...