[GRADLE-386] javadoc generation fails Created: 02/Feb/09  Updated: 04/Jan/13  Resolved: 03/May/09

Status: Resolved
Project: Gradle
Affects Version/s: 0.5.2
Fix Version/s: None

Type: Bug
Reporter: Stefan Groschupf Assignee: Tom Eyckmans
Resolution: Fixed Votes: 0

Issue Links:
dependent on GRADLE-360 Let the Gradle javadoc task expose al... Resolved


I tried different project including the gradle sources. The javadoc tasks always fails. Digging into it, shows that failonerror is actually hard set to true.
What of course will let the javadoc generation fail as soon there is the smallest error in the documentation.
ant.javadoc([destdir: destDir, failonerror: true, verbose: verbose] + otherArgs)
I suggest to make this parameter driven und by default set failonerror to false.
Changing this will fail the JavaProjectIntegrationTest though. What is kind of strange test, since it negative test the javadoc generation but not positive generation.

Anyhow I can generate not distributions of any gradle build project since javadoc always fails. So I think worth a blocker and a maintenance release.

Comment by Tom Eyckmans [ 23/Feb/09 ]

Hi Stefan,

I'll include a fix for this with the overall Javadoc improvements.



Comment by Tom Eyckmans [ 13/Mar/09 ]

Hi Stefan,

I've looked into this some more and added a failOnError switch on the Javadoc task. However I've kept the current default (true).

Successfull generation is also tested, but in the JavadocTest class with mocks.

Documentation problems are warnings in Javadoc so I'm unsure what causes the Gradle build to fail in your environment. Only things that would really cause Javadoc to fail should be errors, could you provide some more information about the problems you are experiencing?



Generated at Wed Jun 30 11:28:48 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.