[
http://jira.codehaus.org/browse/MJAVADOC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190216#action_190216
]
Francis De Brabandere edited comment on MJAVADOC-214 at 9/8/09 7:17 AM:
------------------------------------------------------------------------
I have seen this issue when you do a "mvn clean install site" on a multimodule
build where javadoc report aggregation is enabled. And this only after changing
to a new version. (it's indicated in the logs that he does not seem to find
snapshots)
The fix was to do a "mvn clean install" first to get the snapshots in the local
repo or to disable report generation.
was (Author: francisdb):
I have seen this issue when you do a "mvn clean install" on a multimodule
build where javadoc report aggregation is enabled. And this only after changing
to a new version. (it's indicated in the logs that he does not seem to find
snapshots)
The fix was to do a "mvn clean install" first to get the snapshots in the local
repo or to disable report generation.
> test javadoc goal uses incorrect dependency classpath
> -----------------------------------------------------
>
> Key: MJAVADOC-214
> URL: http://jira.codehaus.org/browse/MJAVADOC-214
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: Brett Porter
>
> according to this report:
> http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19158787.html
> The test javadoc goal is not using the test classpath dependencies.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
