[jira] Commented: (MJAVADOC-140) test-javadoc run in aggregate mode does not pass correct classpath to javadoc tool

[ http://jira.codehaus.org/browse/MJAVADOC-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103983 ] Vincent Siveton commented on MJAVADOC-140: -- My guess is that TestJavadocReport.getTestArtifacts(...) needs to use

[jira] Commented: (MJAVADOC-140) test-javadoc run in aggregate mode does not pass correct classpath to javadoc tool

[ http://jira.codehaus.org/browse/MJAVADOC-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103999 ] John Allen commented on MJAVADOC-140: - except I don't think getExecutionProject can be relied upon to always return a

[jira] Commented: (MJAVADOC-140) test-javadoc run in aggregate mode does not pass correct classpath to javadoc tool

[ http://jira.codehaus.org/browse/MJAVADOC-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103589 ] Vincent Siveton commented on MJAVADOC-140: -- Thanks. FYI, the javadoc plugin uses an IT approach for real

[jira] Commented: (MJAVADOC-140) test-javadoc run in aggregate mode does not pass correct classpath to javadoc tool

[ http://jira.codehaus.org/browse/MJAVADOC-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103594 ] John Allen commented on MJAVADOC-140: - I only saw maven-javadoc-plugin\src\it\MJAVADOC-110 under IT, do the ITs reside

[jira] Commented: (MJAVADOC-140) test-javadoc run in aggregate mode does not pass correct classpath to javadoc tool

[ http://jira.codehaus.org/browse/MJAVADOC-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103597 ] Vincent Siveton commented on MJAVADOC-140: -- No. But you could create IT tests here if you want or need.