Brett Cave wrote: > > This means that "provided" dependencies in upstream projects will need to > be > re-declared as provided dependencies in downstream projects.... >
I don't think so. Maven's "provided" scope is not transitive. Therefore it is not necessary to include a dependency with scope "provided" in a published POM. If a downstream project needed the provided dependency, it would have to redeclare it even with Maven. See: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html -- 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-tp3409118p3409421.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
