On Aug 25, 2008, at 10:41 PM, Hans Dockter wrote:
Hi,
currently our CI build is failing. One reason for this is that need
to upgrade to a new wrapper version, which would be easy to do. But
then my changes have also broken the javadoc task in trunk. I don't
know yet why this is the case. Applying Javadoc against the Gradle
project itself leads to errors and finally a failed build. I'm off
to bed now and try to fix this tomorrow morning.
This is fixed now. The class DefaultConventionsToPropertiesMapping
has been causing the javadoc errors. I had refactored it from Groovy
to Java. I don't know why it is causing javadoc errors. I have
excluded it from the javadoc's for now. This also points to the
issue, that Gradle's packaging can be improved. In the next days I
will start a discussion on the dev list about this issue.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
