hi gradle-community,
i have a question regarding exclusion by the provided* Configurations
situation:
build of a war
dependencies {
compile 'org.clojure:clojure:1.2.0' (***)
compile 'org.clojure:clojure-contrib:1.2.0'
compile 'compojure:compojure:0.5.3'
compile 'ring:ring-core:0.3.4' (**)
compile 'ring:ring-devel:0.3.4'
compile 'ring:ring-servlet:0.3.4'
providedCompile 'javax.servlet:servlet-api:2.5'
providedCompile 'ring:ring-jetty-adapter:0.3.4' (*)
}
ring-jetty-adapter (*) has a dependeny on ring-core-0.3.4 (**), jetty et al.
<dependency>
<groupId>ring</groupId>
<artifactId>ring-core</artifactId>
<version>0.3.4</version>
</dependency>
<dependency>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty</artifactId>
<version>6.1.14</version>
</dependency>
ring-core (**) has a dependeny on clojure-1.2.0 (***) et al.
<dependency>
<groupId>org.clojure</groupId>
<artifactId>clojure</artifactId>
<version>1.2.0</version>
</dependency>
my problem:
clojure-1.2.0 is resolved for compile but not packed
into the war because it's excluded via providedCompile.
my question:
should'nt clojure-1.2.0 be packed into the war because
the compile-configuration has a dependency on it and
thus it is (probably) needed during runtime ?
of course jetty should still be excluded from being packed
into the war.
gruesse
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Exclusion-by-the-provided-Configurations-tp3338016p3338016.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
