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.

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.

-Paul

Russel Winder wrote:
On Thu, 2009-12-10 at 21:40 +0000, Russel Winder wrote:
Levi,

name doesn't work for me as I have a sub-block within the subproject
block, but project.name works nicely for me.  Thanks muchly.

Except that it doesn't work -- at least not as I expected.  I suspect
though this is because Gradle is working correctly!

The actual example I had was:

        subprojects {
                . . .
                groovydoc {
. . . if ( project.name != 'gant_gradle1.5' ) { docTitle = 'blah' } . . . }
                . . .
        }

However, when it comes to execute :gant_groovy1.5:groovydoc, docTitle is
still defined!  I think this must be because there is a cumulative
aspect to definitions used in this multiproject framework.
On Thu, 2009-12-10 at 19:03 +0100, Levi Hoogenberg wrote:
name works for me, project.name probably would as well:

subprojects {
    // ...

    if (name != 'tests') {
        // ...

        tasks.test.enabled = false
    }
}

Regards,
  Levi

On Thu, Dec 10, 2009 at 4:48 PM, Russel Winder
<[email protected]> wrote:
        The context is the Gant build and specifically the attributes
        of the
        groovydoc task.
The Gant task is structured as a quartet of projects all using
        the same
        source.  The subprojects allow for building with the four
        different
        families of Groovy.  All the common specifications are in the
        subprojects section, it all seems to work fine.  The problem I
        have is
        that Groovy 1.5.8 version of GroovyDoc doesn't understand the
        doctitle
        attribute whereas all later versions do.  I want to avoid
        replicating
        the specifications I just want to have something like:
subprojects {
               . . .
                 groovydoc {
                   packageNames = [ 'gant.*' ,
        'org.codehaus.gant.*' ] // Why have to have this when not
        needed for javadoc?
                   overview = 'overview.html'
                   includePrivate = false
                   encoding = 'UTF-8'
                   use = true
                   author = 'true'
                   version = 'true'
                   windowTitle = packageTitle
                   if ( subproject != 'gant_groovy1.5' ) docTitle =
        packageTitle
                   header = packageTitle
                   footer = copyrightString
                 }
               }
The question is how to properly refer to the subproject name
        in the subproject specification.
Thanks. --
        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






---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email


Reply via email to