Feb 17th, 2013, 02:20 PM
Excluding Groovy dependencies from Gradle projects or re-ordering the classpath
I've got a problem similar to this thread but the issue is that the conflicting dependency in question (servlet-api-2.4) is being included due to the Groovy Libraries, not the Gradle DSL support.
Disabling DSL support and refreshing dependencies doesn't appear to have any effect on the Groovy Libraries entries. If there's no way to eliminate the Groovy libraries from the classpath for Gradle projects in STS, is there at least a way to re-order the classpath so the dependencies I've specified in my Gradle build file come first?
If anyone is interested in reproducing this, just check out Jon Brisbin's spring-data-rest-webmvc project and import it into STS. It'll immediately complain about RestExporterWebInitializer because it uses new Servlet API 3.0 methods and STS is picking up 2.4.
Screen Shot 2013-02-17 at 3.15.54 PM.jpg
Tags for this Thread