Upstream is gradle, have just migrated it from maven. it is a java project (i.e. jar). Thats when the dependency issue started.
maven: <scope>provided</scope> 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. On Fri, Mar 4, 2011 at 12:52 PM, Peter Niederwieser <[email protected]>wrote: > If the upstream project uses the war plugin, the correct solution is to put > servlet-api on the providedCompile or providedRuntime class path of the > upstream project. Or is the upstream project built with Maven? > > -- > 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-tp3409118p3409272.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 > > >
