Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Not A Bug
-
Affects Version/s: 2.6.1
-
Fix Version/s: None
-
Labels:None
-
Number of attachments :
Description
After upgrading from 2.6 to 2.6.1 our Apache Cayenne builds got broken. The problem is in module with no public or protected sources (there's only a package-private class). Now, after infamous message "'org.apache.maven.plugins:maven-javadoc-plugin:2.6:javadoc' has not be
previously called for the project ..." build fails and creates an error report. In the report:
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] An error has occurred in JavaDocs report generation:
Exit code: 1 - javadoc: error - No public or protected classes found to document.
Command line was: C:\Progra~1\Java\jdk1.6.0_13\jre\..\bin\javadoc.exe @options @packages
Refer to the generated Javadoc files in 'C:\Project\cayenne-parent\framework\cayenne-jdk1.6-unpublished\target\site\apidocs' dir.
Issue Links
- relates to
-
MJAVADOC-306
javadoc fails when no classes are found to document
-
And one more thing. I'm not sure about the reason, but both in 2.6 and 2.6.1, when we try to disable this new feature by setting detectOfflineLinks=false, Maven build succeeds, but Hudson cannot publish JavaDoc. Seems like some docs were not properly built. See error at very end of log:
http://hudson.zones.apache.org/hudson/job/Cayenne-trunk/jdk=JDK%201.5%20%28latest%29/28/console
FATAL: /export/home/hudson/hudson/jobs/Cayenne-trunk/workspace/jdk/JDK 1.5 (latest)/trunk/framework/cayenne-jdk1.5-unpublished/target/site/apidocs not found.