Rene Groeschke wrote: > > Anybody an idea how to solve this? any known workarounds? >
Gradle intentionally no longer puts Maven classes on the build script class path, so you can't reference them anymore. For your use case, Gradle should really offer a solution that doesn't require you to do this. Instead, you should be able to add in the excludes in a POM builder style fashion. Please raise an issue for this. In the mean time, you'll have to work around it in some way. For example, you could try to declare those dependencies with the POM builder. Or you could get hold of an exclude that's already there, get its Class, and create a new instance reflectively. Out of curiosity, why do you post-process the POM rather than setting the excludes in Gradle's dependencies section? -- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Blog: http://pniederw.wordpress.com Twitter: @pniederw -- View this message in context: http://gradle.1045684.n5.nabble.com/Classloader-issues-in-my-pom-configuration-tp4576879p4581597.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
