1. Your project dependency declaration is missing a colon.
2. It would be easy to make jsr166's testCompile configuration public, but
it wouldn't get you any further because this configuration only contains
jsr166's test compile dependencies.
3. You could create a Jar (not necessarily a project) for the TCK class(es)
to be shared and expose it via a custom configuration. An even simpler way
would be:
testCompile project(":jsr166").sourceSets.test.classes // could be filtered
for particular classes
Not sure if there is a downside to this approach.
--
Peter Niederwieser
Developer, Gradle
http://www.gradle.org
Trainer & Consultant, Gradle Inc.
http://www.gradle.biz
Creator, Spock Framework
http://spockframework.org
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Multi-Project-builds-and-fine-grain-dependencies-tp3400363p3400608.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
