maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Razumovsky (JIRA)" <>
Subject [jira] Commented: (MJAVADOC-274) Regression in 2.6.1 - modules with no sources cause an error
Date Thu, 05 Nov 2009 21:19:55 GMT


Andrey Razumovsky commented on MJAVADOC-274:

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:

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.

> Regression in 2.6.1 - modules with no sources cause an error
> ------------------------------------------------------------
>                 Key: MJAVADOC-274
>                 URL:
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.6.1
>            Reporter: Andrey Razumovsky
> 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
> previously called for the project ..." build fails and creates an error report. In the
> [INFO] ------------------------------------------------------------------------
> [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'

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message