Adam Murdoch-3 wrote:
>
> In general, there isn't. But there might be a workaround, depending on why
> you need the conflict resolution.
>
hi adam,
thanks for the answer and sorry for the delay ...
here is such a situation:
dependencies {
compile 'org.clojure:clojure:1.2.0'
compile 'org.clojure:clojure-contrib:1.2.0'
compile 'enlive:enlive:1.0.0-SNAPSHOT'
}
enlive has a dependency on clojure too and defines it
in it's pom like this:
<dependency>
<groupId>org.clojure</groupId>
<artifactId>clojure</artifactId>
<version>[1.1.0,)</version>
</dependency>
which means "resolve against latest release of
clojure".
so during the build clojure-1.2.0 is evicted:
:: evicted modules:
org.clojure#clojure;1.2.0 by [org.clojure#clojure;1.3.0-alpha4] in [compile]
i would like to avoid the eviction and force resolving
clojure-1.2.0.
gruesse
btw: mikel brandmeier has greatly improved his clojure-plugin
for gradle (clojuresque) lately. there are some outstanding
features though ... like support for the clojure.test and selective
aot-compile.
--
View this message in context:
http://gradle.1045684.n5.nabble.com/custom-dependency-conflict-resolver-tp3205266p3336242.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
