[
https://jira.codehaus.org/browse/MJAVADOC-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308548#comment-308548
]
Benson Margulies commented on MJAVADOC-274:
-------------------------------------------
Since the javadoc tool itself does not like this situation, why is it up to us
to work around?
I propose to close this based on Hervé's observation.
> Regression in 2.6.1 - modules with no sources cause an error
> ------------------------------------------------------------
>
> Key: MJAVADOC-274
> URL: https://jira.codehaus.org/browse/MJAVADOC-274
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.6.1
> Reporter: Andrey Razumovsky
> Assignee: John Casey
> Attachments: MJAVADOC-274.zip
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
