I am attempting to use a custom configuration to resolve the artifacts
from another project in a multi-project build as follows:
In proj3 -
dependencies {
//... clipped normal compile dependencies.
// Including declaring a company internal maven repo ...
compile project(':proj1')
addConfiguration('signer')
signer project(':proj1')
signer project(':proj2')
}
// inside task
String path = dependencies.signer.asPath
This results in :
Execution failed for task ':proj3:sign'.
Cause: Not all dependencies could be resolved!
Gradle appears to be trying to resolve the artifact from proj1 using my
company internal maven repo instead of from the jar it created in the
build directory of proj1.
These types of project dependencies work fine for the compile
configuration, but apparently the Java plugin is doing something special
to make this work. It doesn't work as I expect for a custom
configuration. What can I do to get this to resolve to the project jars
without going to the repo?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
