You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@groovy.apache.org by Mario Garcia <ma...@gmail.com> on 2016/06/29 10:50:44 UTC

Trying to understand why groovydoc task needs groovy-all in Gradle 2.13 / 2.14

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

Re: Trying to understand why groovydoc task needs groovy-all in Gradle 2.13 / 2.14

Posted by Mario Garcia <ma...@gmail.com>.
Nice!

Although in the project I'm mentioning I think we're ok by using groovy-all
(it's already added by other transitive dependencies) I have other projects
where I'll definitely use this solution/workaround.

Thanks Schalk :)

2016-06-29 13:10 GMT+02:00 Schalk Cronjé <ys...@gmail.com>:

> 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
>
>

Re: Trying to understand why groovydoc task needs groovy-all in Gradle 2.13 / 2.14

Posted by Schalk Cronjé <ys...@gmail.com>.
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