On Fri, 2011-02-25 at 10:35 -0800, Peter Niederwieser wrote: > 1. Your project dependency declaration is missing a colon.
I think you must have taken a peek at the Git repository before I fixed
the colons. At least I think I did, is there one I missed. These
colons are weird you need them in the references but they seem to be
optional in the project definition.
> 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.
I have changed tack and separated out the TCK as a separate project
rather than being the test of the code. I think this is needed to solve
the bootstrap problem -- testing needs the jar but you can have project
self references. It seems easier just to split things.
> 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.
Thanks for this idea, I shall cogitate and integrate.
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected]
41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected]
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
