[
http://jira.codehaus.org/browse/MJAVADOC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161880#action_161880
]
Josh Devins commented on MJAVADOC-214:
--------------------------------------
Just a confirmation that I also encountered this problem with version 2.4, but
since upgrading to 2.5 it seems to work fine. The project structure where I saw
this was perhaps the problem. It looked like this:
project/pom.xml <-- this is where I would run from to reproduce the problem
project/project-parentPom/pom.xml <-- the parent pom was a module of the "root"
project pom
project/project-anotherArtifact/pom.xml <-- this is where the failure was
occurring for test dependencies
But as I mentioned, upgrading to 2.5 solved the problem for this project and
structure (although I don't advocate using such a project structure!).
> 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
