On Fri, 2009-12-11 at 11:47 -0500, Paul Speed wrote: > Note: I don't know if this is changed recently but in the past, inside a > subprojects block 'project' will refer to only the last project loaded. > I use 'delegate' now instead... since that's supposed to be the > sub-project within the subprojects closure.
My problem I guess is that I am still stuck a bit in Gradle 0.5 :-)
If users have to think in terms of delegate, I suspect the abstractions
have broken -- this is a Groovy internal thing that should really be
exposed outside the Gradle internals.
My feeling is that project.name is the right handle for something in a
subproject or all specification. I guess the problem is that the
semantics of subproject is not quite what I think it is or the groovydoc
specification withint he subproject specification is causing weirdness.
> I don't know if it changes inside the groovydoc closure as this is all
> still a little new to me.
>
> ...and maybe it doesn't apply here but you might dump a debug print of
> project.name just to double-check.
I suspect my problem is too few painkillers and/or lack of whisky but I
am not sure what you are proposing by "dump a debug print".
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
