You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/08/26 12:52:26 UTC
[jira] Created: (MJAVADOC-214) test javadoc goal uses incorrect
dependency classpath
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
[jira] Commented: (MJAVADOC-214) test javadoc goal uses incorrect
dependency classpath
Posted by "Tan Quach (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146095#action_146095 ]
Tan Quach commented on MJAVADOC-214:
------------------------------------
I am getting these same errors, however here is some additional information:
When I run "mvn javadoc:test-javadoc" from within either a standalone project or sub-module project that has test sources, it works fine.
When I run "mvn javadoc:test-javadoc" from a parent project, it fails when it gets to the sub-module.
> 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
[jira] Commented: (MJAVADOC-214) test javadoc goal uses incorrect
dependency classpath
Posted by "Chris Wilper (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148718#action_148718 ]
Chris Wilper commented on MJAVADOC-214:
---------------------------------------
I had the same problem (also present when aggregate=true), and it went away when upgrading to 2.5
> 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
[jira] Closed: (MJAVADOC-214) test javadoc goal uses incorrect
dependency classpath
Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Siveton closed MJAVADOC-214.
------------------------------------
Resolution: Cannot Reproduce
Seems to be fix somewhere between 2.4 and 2.6...
> 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
[jira] Commented: (MJAVADOC-214) test javadoc goal uses incorrect
dependency classpath
Posted by "Rodolfo Rothganger (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150394#action_150394 ]
Rodolfo Rothganger commented on MJAVADOC-214:
---------------------------------------------
I´ve got a similar problems regarding annotations not found by the plugin. In my project there is a parent POM declaring FindBugs annotations as "compile" scoped dependencies.
While tring to deploy an artifact with the above POM as parent produced the following error:
"
a "java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be cast to com.sun.javadoc.AnnotationTypeDoc
at com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46)
at com.sun.tools.doclets.internal.toolkit.util.Util.isDeprecated(Util.java:811)
"
To work around the problem I´ve declared the compile scoped annotations as dependencies of the plugin itself.
> 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
[jira] Commented: (MJAVADOC-214) test javadoc goal uses incorrect
dependency classpath
Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146313#action_146313 ]
Vincent Siveton commented on MJAVADOC-214:
------------------------------------------
Since I am unable to reproduce it, I need a test case.
bq. When I run "mvn javadoc:test-javadoc" from a parent project, it fails when it gets to the sub-module.
Could you try with javadoc:test-aggregate (introduced in Javadoc plugin 2.5)
> 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
[jira] Commented: (MJAVADOC-214) test javadoc goal uses incorrect
dependency classpath
Posted by "Josh Devins (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MJAVADOC-214) test javadoc goal uses incorrect
dependency classpath
Posted by "Roger Pack (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157609#action_157609 ]
Roger Pack commented on MJAVADOC-214:
-------------------------------------
for 2.4:
<dependency>
<groupId>org.testng</groupId>
<artifactId>testng</artifactId>
<version>5.8</version>
<classifier>jdk15</classifier>
<!--scope>test</scope-->
</dependency>
> 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
[jira] Commented: (MJAVADOC-214) test javadoc goal uses incorrect
dependency classpath
Posted by "Francis De Brabandere (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190216#action_190216 ]
Francis De Brabandere commented on MJAVADOC-214:
------------------------------------------------
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
[jira] Commented: (MJAVADOC-214) test javadoc goal uses incorrect
dependency classpath
Posted by "Christian Decker (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157330#action_157330 ]
Christian Decker commented on MJAVADOC-214:
-------------------------------------------
How would you do that?
> 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
[jira] Issue Comment Edited: (MJAVADOC-214) test javadoc goal uses
incorrect dependency classpath
Posted by "Francis De Brabandere (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MJAVADOC-214) test javadoc goal uses incorrect
dependency classpath
Posted by "Peter Mount (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183929#action_183929 ]
Peter Mount commented on MJAVADOC-214:
--------------------------------------
I've also been hit with this issue whilst running 2.1.0 recently and currently whilst running 2.2.0, so if it was fixed between 2.4 and 2.6 it's now broken again :-(
> 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