Hi Pieter,
On Jul 10, 2008, at 11:52 AM, pieter.smit wrote:
hi Hans,
I did the following:
subprojects {
task("${project.name}_jar").destinationDir = file(distDir)
}
distDir is a property defined by the Java plugin. This is already of
type file and points to build/distributions. You might have
overwritten it with a string property of your own. Than of course the
file(distDir) statements makes sense.
This causes the libs task to output all my subprojects generated
jars in a
single directory of my choice, which was what I intended. What I
didn't
intend was the following:
missing artifact com.bla#bla-interface;1.0!bla-interface.jar:
/home/pieter/development/trunk/bla-interface/build/bla-
interface-1.0.jar
file does not exist
/home/pieter/development/trunk/bla-interface/build/distributions/
bla-interface-1.0.jar
file does not exist
published ivy to
/home/pieter/development/trunk/build-resolver/com.bla/bla-interface/
1.0/ivys/ivy.xml
this happens when I try to compile a project with the depency:
dependencies {
compile project(':bla-interface'),
}
How can I tell the resolver to find the project in my new location?
dependencies {
artifactPatterns << someRootPath + "/[artifact]-[revision](-
[classifier]).[ext]")
}
Sorry for not having a look at this earlier (never mention that you
have found a work around ;))
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
