Brett Cave wrote: > > Used a custom "provided" configuration, but managed to get it working by > using compile.exclude module: 'servlet-api' along with a new "provided" > configuration that includes the servlet API on the compile classpath. >
Yes, if the upstream project is a Jar project, you'd have to manually introduce a "provided" configuration (in the upstream project!). However, I don't see the need for an exclude. I think that Gradle should automatically offer a providedCompile/providedRuntime configuration for all projects, not just for those using the war plugin. Consider voting for http://jira.codehaus.org/browse/GRADLE-784. -- Peter Niederwieser Developer, Gradle http://www.gradle.org Trainer & Consultant, Gradleware http://www.gradleware.com Creator, Spock Framework http://spockframework.org -- View this message in context: http://gradle.1045684.n5.nabble.com/gradle-maven-repository-and-pom-dependencies-tp3409118p3409313.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
