groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mario Garcia <>
Subject Trying to understand why groovydoc task needs groovy-all in Gradle 2.13 / 2.14
Date Wed, 29 Jun 2016 10:50:44 GMT
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 ?


View raw message