Hans.. got a very interesting one just now.
build file:
usePlugin 'groovy' //note, I know this is deprecated/use apply
configurations.compile.transitive = true
repositories {
mavenCentral()
}
dependencies {
groovy 'org.codehaus.groovy:groovy-all:1.7.0'
compile 'org.apache.poi:poi:3.5-FINAL'
compile 'org.apache.poi:poi-contrib:3.5-FINAL'
compile 'org.apache.poi:poi-scratchpad:3.5-FINAL'
compile 'org.apache.poi:poi-ooxml:3.5-FINAL'
compile
'org.codehaus.groovy.modules.http-builder:http-builder:0.5.0-RC3'
}
task copyRuntimeDependencies(dependsOn:
configurations.runtime.buildArtifacts, type: Copy) {
into('lib')
from configurations.runtime
from configurations.runtime.allArtifacts*.file
}
if I do gradle -n, I get the report.. build is successful.. downloads
all the dependencies.. Victory!
if I do:
gradle copyRuntimeDependencies
It downloads gradle 1.7-rc2.
Now, what is odd, is that 1.7-rc2 is *not* in the gradle -n report.
I imagine this, possibly, is because that "task" is from an example
for 0.8 and maybe now somethign in 0.9 is giving it headaches?
Any thoughts? I reply on a task, "like that" to make a lib folder so
all the eclipse users can get their jars heh
Thanks,
Roger
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
