groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Schalk Cronjé <ysb...@gmail.com>
Subject Re: Trying to understand why groovydoc task needs groovy-all in Gradle 2.13 / 2.14
Date Wed, 29 Jun 2016 11:10:17 GMT
On 29/06/2016 11:50, Mario Garcia wrote:
> I'm trying to execute a project using gradle 2.13 / 2.14 and it fails 
> when executing groovydoc saying:
>
> groovydoc doesn't support the "noTimestamp" attribute
>
> Checking gradle documentation it's saying you should be using 
> groovy-all, but sometimes I may not want to use the whole groovy-all jar.
>
> Does anyone know why is this ? Is this a Gradle bug, it's something 
> that changed in groovydoc ?
>
> Mario
I cannot answer the bug question, but AFAIK you can let groovydoc use a 
different classpath. Something like

    configurations {
       forGroovyDoc
    }

    dependencies {
       forGroovyDoc 'org.....groovy-all...'
    }

    groovydoc {
       groovyClasspath = configurations.forGroovyDoc
    }

HTH


-- 
Schalk W. Cronjé
Twitter / Ello / Toeter : @ysb33r


Mime
View raw message