Michael Parmeley

This has been a long-standing issue with this plugin, there have been several issues opened regarding it, I believe this was the first one: https://github.com/gigaSproule/swagger-gradle-plugin/issues/132

This workaround does not work for me. After applying the workaround the classes in my project itself can't be found. Whereas before it just couldn't find any classes in my...

> By adding the flag to skip including super types and also adding the above work around my problems have been solved. Thanks all! @jonnii Which flag are you referring...

@jonnii Oh, I see you are referring to the `expandSuperTypes = false` Including that plus the workaround does indeed work for me as well.

I am having these issues too. Tons of "could not get type for name" for spring classes as well as classes generated from annotation processors.

Yeah, it is definitely the reflection code complaining. I am using Java 8. Works fine with Gradle 4.10 and 1.0.0 of this plugin. Have to use a newer version of...

> Also, @mjparme what is the relationship between MutableAclService and your annotated classes? @gigaSproule MutableAclService is found in a dependency of my code, it isn't directly referenced by my annotated...

@gigaSproule FWIW, I get that error "could not get type for name...from any classloader" for pretty much every class my code references that are in my dependencies, here is another...

I have created a test spring boot application that recreates the problem. Just extract the project, cd into the project and execute `./gradlew generateS` you will see it complain: ```...

> Seems like as soon as any package specified in `locations` appears inside any jar on classpath, these errors will appear. This actually appears to be the trigger for the...