> This is fixed now.
>
ah - thats nice. i have a working build-script like this now:
apply id: 'java'
apply id: 'custom-resolvers'
group = 'myCompany'
version = '1.0'
repositories {
customDownstreamRepos()
}
uploadArchives {
repositories {
customUpstreamRepos()
}
}
dependencies {
compile 'apache:commons-lang:2.1'
testCompile 'junit:junit:3.8.1'
}
(customDownstreamRepos() and customUpstreamRepos() are defined
via CustomResolversPluginConvention)
the main-benefit over the previous use of plugin 'custom-resolvers'
is, that build-script-authors have control over the position of
'custom-resolvers' in the resolver-chain. for instance:
repositories {
mavenCentral()
customDownstreamRepos()
}
resolves against mavenCentral first where as:
repositories {
customDownstreamRepos()
mavenCentral()
}
resolves against customRepos first
Gruesse ...
--
View this message in context:
http://old.nabble.com/Can-I-add-other-dependency-resolvers--tp27758967p27872468.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
