I'm afraid your proposals doesn't seem to work.
Where do you put the classpath element?
In Fact, my operational use case are:
For each target script:
1. Retrieving a plugin
2. Declaring the plugin
3. Configuring it
buildscript {
repositores{
new org.apache.ivy.plugins.resolver.URLResolver()) {
name="Artifactory"
url= repositoryURL
addArtifactPattern "$url/[organisation]/[artifact]-[revision].[ext]"
addIvyPattern "$url/[organisation]/[artifact]-ivy-[revision].xml"
}
dependencies{
classpath "com.myorganisation:myplugin:1.0"
}
}
apply id: 'mypluginid'
configure(myConventionObject){
...
}
I've got lots of scripts that follows the same behavior with the same
plugin.
In my opinion, regarding this case, externalize the buildscript section in a
common buildscript makes sense.
--
View this message in context:
http://old.nabble.com/%27buildscript%27-section-%2B-%27apply-url%27-together-tp27720789p27726664.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
