You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Chris Tait (JIRA)" <ji...@codehaus.org> on 2009/10/30 06:28:26 UTC
[jira] Created: (MSITE-432) Incorrect classpath is used when site
plugin/phase launches javadoc command
Incorrect classpath is used when site plugin/phase launches javadoc command
---------------------------------------------------------------------------
Key: MSITE-432
URL: http://jira.codehaus.org/browse/MSITE-432
Project: Maven 2.x Site Plugin
Issue Type: Bug
Affects Versions: 2.0.1, 2.0-beta-7
Environment: Maven 2.2.1
Reporter: Chris Tait
Priority: Minor
Attachments: maven-projects.zip
When invoking the site plugin (with javadoc reporting enabled) for a project that depends on both the main artifact and the tests artifact of another project, the classpath passed to the javadoc command is incorrect.
For example:
Project A produces the following artifacts:
- ProjectA-version.jar (main artifact)
- ProjectA-version-tests.jar (test classes)
And project B has dependencies similar to this:
{code}<dependency>
<groupId>...</groupId>
<artifactId>Project1</artifactId>
<version>...</version>
</dependency>
<dependency>
<groupId>...</groupId>
<artifactId>Project1</artifactId>
<version>...</version>
<classifier>tests</classifier>
<scope>test</scope>
</dependency>{code}
Then only one of the jars is included in the classpath passed to the javadoc command. (Normally it seems to be the main artifact, although on one of my projects it was the tests artifact instead.) This causes lots of warnings, or for some projects causes the build to fail.
Note that if I explicitly run the javadoc goals (i.e. "mvn javadoc:javadoc" or "mvn javadoc:test-javadoc") then the classpath is populated correctly and no errors are shown. It's only when the site plugin/phase launches it that the classpath is wrong. I've also found that the order of the dependencies within the POM file seems to make a difference in some cases.
I've attached a zip file containing two projects to reproduce this. To run it:
# run {{mvn install}} on project1
# run {{mvn site}} on project2 (to see the warnings) or {{mvn javadoc:test-javadoc}}
The warning looks like this:
{code}[WARNING] Javadoc Warnings
[WARNING] D:\code\EclipseWorkspaces_chris\PaymentCard\project3\src\main\java\repro3\MyClass3.java:3: cannot find symbol
[WARNING] symbol : class MyClass1
[WARNING] location: package repro1
[WARNING] import repro1.MyClass1;
[WARNING] ^{code}
--
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: (MSITE-432) Incorrect classpath is used when site
plugin/phase launches javadoc command
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MSITE-432.
---------------------------------
Resolution: Duplicate
> Incorrect classpath is used when site plugin/phase launches javadoc command
> ---------------------------------------------------------------------------
>
> Key: MSITE-432
> URL: http://jira.codehaus.org/browse/MSITE-432
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-7, 2.0.1
> Environment: Maven 2.2.1
> Reporter: Chris Tait
> Priority: Minor
> Attachments: maven-projects.zip
>
>
> When invoking the site plugin (with javadoc reporting enabled) for a project that depends on both the main artifact and the tests artifact of another project, the classpath passed to the javadoc command is incorrect.
> For example:
> Project A produces the following artifacts:
> - ProjectA-version.jar (main artifact)
> - ProjectA-version-tests.jar (test classes)
> And project B has dependencies similar to this:
> {code}<dependency>
> <groupId>...</groupId>
> <artifactId>Project1</artifactId>
> <version>...</version>
> </dependency>
> <dependency>
> <groupId>...</groupId>
> <artifactId>Project1</artifactId>
> <version>...</version>
> <classifier>tests</classifier>
> <scope>test</scope>
> </dependency>{code}
> Then only one of the jars is included in the classpath passed to the javadoc command. (Normally it seems to be the main artifact, although on one of my projects it was the tests artifact instead.) This causes lots of warnings, or for some projects causes the build to fail.
> Note that if I explicitly run the javadoc goals (i.e. "mvn javadoc:javadoc" or "mvn javadoc:test-javadoc") then the classpath is populated correctly and no errors are shown. It's only when the site plugin/phase launches it that the classpath is wrong. I've also found that the order of the dependencies within the POM file seems to make a difference in some cases.
> I've attached a zip file containing two projects to reproduce this. To run it:
> # run {{mvn install}} on project1
> # run {{mvn site}} on project2 (to see the warnings) or {{mvn javadoc:test-javadoc}}
> The warning looks like this:
> {code}[WARNING] Javadoc Warnings
> [WARNING] D:\code\EclipseWorkspaces_chris\PaymentCard\project3\src\main\java\repro3\MyClass3.java:3: cannot find symbol
> [WARNING] symbol : class MyClass1
> [WARNING] location: package repro1
> [WARNING] import repro1.MyClass1;
> [WARNING] ^{code}
--
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: (MSITE-432) Incorrect classpath is used when site
plugin/phase launches javadoc command
Posted by "Ryan Lea (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208560#action_208560 ]
Ryan Lea commented on MSITE-432:
--------------------------------
I've also faced this issue and it blocks to default behaviour of the maven-release-plugin release:perform goal.
> Incorrect classpath is used when site plugin/phase launches javadoc command
> ---------------------------------------------------------------------------
>
> Key: MSITE-432
> URL: http://jira.codehaus.org/browse/MSITE-432
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-7, 2.0.1
> Environment: Maven 2.2.1
> Reporter: Chris Tait
> Priority: Minor
> Attachments: maven-projects.zip
>
>
> When invoking the site plugin (with javadoc reporting enabled) for a project that depends on both the main artifact and the tests artifact of another project, the classpath passed to the javadoc command is incorrect.
> For example:
> Project A produces the following artifacts:
> - ProjectA-version.jar (main artifact)
> - ProjectA-version-tests.jar (test classes)
> And project B has dependencies similar to this:
> {code}<dependency>
> <groupId>...</groupId>
> <artifactId>Project1</artifactId>
> <version>...</version>
> </dependency>
> <dependency>
> <groupId>...</groupId>
> <artifactId>Project1</artifactId>
> <version>...</version>
> <classifier>tests</classifier>
> <scope>test</scope>
> </dependency>{code}
> Then only one of the jars is included in the classpath passed to the javadoc command. (Normally it seems to be the main artifact, although on one of my projects it was the tests artifact instead.) This causes lots of warnings, or for some projects causes the build to fail.
> Note that if I explicitly run the javadoc goals (i.e. "mvn javadoc:javadoc" or "mvn javadoc:test-javadoc") then the classpath is populated correctly and no errors are shown. It's only when the site plugin/phase launches it that the classpath is wrong. I've also found that the order of the dependencies within the POM file seems to make a difference in some cases.
> I've attached a zip file containing two projects to reproduce this. To run it:
> # run {{mvn install}} on project1
> # run {{mvn site}} on project2 (to see the warnings) or {{mvn javadoc:test-javadoc}}
> The warning looks like this:
> {code}[WARNING] Javadoc Warnings
> [WARNING] D:\code\EclipseWorkspaces_chris\PaymentCard\project3\src\main\java\repro3\MyClass3.java:3: cannot find symbol
> [WARNING] symbol : class MyClass1
> [WARNING] location: package repro1
> [WARNING] import repro1.MyClass1;
> [WARNING] ^{code}
--
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: (MSITE-432) Incorrect classpath is
used when site plugin/phase launches javadoc command
Posted by "James Ravn (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231600#action_231600 ]
James Ravn edited comment on MSITE-432 at 8/10/10 9:50 AM:
-----------------------------------------------------------
Using <type>test-jar</type> exhibits the same exact issue in 2.2.1. The only workaround I can find is to place the test-jar dependency first - this causes the test javadoc to fail instead of the main javadoc (which maven happily ignores).
was (Author: jsravn):
Using <type>test-jar</type> exhibits the same exact issue in 2.2.1. The only workaround I can find is to place the test-jar dependency first - the test javadoc fails instead of the main javadoc, but maven ignores it.
> Incorrect classpath is used when site plugin/phase launches javadoc command
> ---------------------------------------------------------------------------
>
> Key: MSITE-432
> URL: http://jira.codehaus.org/browse/MSITE-432
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-7, 2.0.1
> Environment: Maven 2.2.1
> Reporter: Chris Tait
> Priority: Minor
> Attachments: maven-projects.zip
>
>
> When invoking the site plugin (with javadoc reporting enabled) for a project that depends on both the main artifact and the tests artifact of another project, the classpath passed to the javadoc command is incorrect.
> For example:
> Project A produces the following artifacts:
> - ProjectA-version.jar (main artifact)
> - ProjectA-version-tests.jar (test classes)
> And project B has dependencies similar to this:
> {code}<dependency>
> <groupId>...</groupId>
> <artifactId>Project1</artifactId>
> <version>...</version>
> </dependency>
> <dependency>
> <groupId>...</groupId>
> <artifactId>Project1</artifactId>
> <version>...</version>
> <classifier>tests</classifier>
> <scope>test</scope>
> </dependency>{code}
> Then only one of the jars is included in the classpath passed to the javadoc command. (Normally it seems to be the main artifact, although on one of my projects it was the tests artifact instead.) This causes lots of warnings, or for some projects causes the build to fail.
> Note that if I explicitly run the javadoc goals (i.e. "mvn javadoc:javadoc" or "mvn javadoc:test-javadoc") then the classpath is populated correctly and no errors are shown. It's only when the site plugin/phase launches it that the classpath is wrong. I've also found that the order of the dependencies within the POM file seems to make a difference in some cases.
> I've attached a zip file containing two projects to reproduce this. To run it:
> # run {{mvn install}} on project1
> # run {{mvn site}} on project2 (to see the warnings) or {{mvn javadoc:test-javadoc}}
> The warning looks like this:
> {code}[WARNING] Javadoc Warnings
> [WARNING] D:\code\EclipseWorkspaces_chris\PaymentCard\project3\src\main\java\repro3\MyClass3.java:3: cannot find symbol
> [WARNING] symbol : class MyClass1
> [WARNING] location: package repro1
> [WARNING] import repro1.MyClass1;
> [WARNING] ^{code}
--
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: (MSITE-432) Incorrect classpath is used when site
plugin/phase launches javadoc command
Posted by "James Ravn (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207652#action_207652 ]
James Ravn commented on MSITE-432:
----------------------------------
I'm also seeing this issue. It makes site-deploy unusable. I have a module running integration tests that depends on common test artifacts of another module. I could skip it, but want to document the tests.
> Incorrect classpath is used when site plugin/phase launches javadoc command
> ---------------------------------------------------------------------------
>
> Key: MSITE-432
> URL: http://jira.codehaus.org/browse/MSITE-432
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-7, 2.0.1
> Environment: Maven 2.2.1
> Reporter: Chris Tait
> Priority: Minor
> Attachments: maven-projects.zip
>
>
> When invoking the site plugin (with javadoc reporting enabled) for a project that depends on both the main artifact and the tests artifact of another project, the classpath passed to the javadoc command is incorrect.
> For example:
> Project A produces the following artifacts:
> - ProjectA-version.jar (main artifact)
> - ProjectA-version-tests.jar (test classes)
> And project B has dependencies similar to this:
> {code}<dependency>
> <groupId>...</groupId>
> <artifactId>Project1</artifactId>
> <version>...</version>
> </dependency>
> <dependency>
> <groupId>...</groupId>
> <artifactId>Project1</artifactId>
> <version>...</version>
> <classifier>tests</classifier>
> <scope>test</scope>
> </dependency>{code}
> Then only one of the jars is included in the classpath passed to the javadoc command. (Normally it seems to be the main artifact, although on one of my projects it was the tests artifact instead.) This causes lots of warnings, or for some projects causes the build to fail.
> Note that if I explicitly run the javadoc goals (i.e. "mvn javadoc:javadoc" or "mvn javadoc:test-javadoc") then the classpath is populated correctly and no errors are shown. It's only when the site plugin/phase launches it that the classpath is wrong. I've also found that the order of the dependencies within the POM file seems to make a difference in some cases.
> I've attached a zip file containing two projects to reproduce this. To run it:
> # run {{mvn install}} on project1
> # run {{mvn site}} on project2 (to see the warnings) or {{mvn javadoc:test-javadoc}}
> The warning looks like this:
> {code}[WARNING] Javadoc Warnings
> [WARNING] D:\code\EclipseWorkspaces_chris\PaymentCard\project3\src\main\java\repro3\MyClass3.java:3: cannot find symbol
> [WARNING] symbol : class MyClass1
> [WARNING] location: package repro1
> [WARNING] import repro1.MyClass1;
> [WARNING] ^{code}
--
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: (MSITE-432) Incorrect classpath is
used when site plugin/phase launches javadoc command
Posted by "James Ravn (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231600#action_231600 ]
James Ravn edited comment on MSITE-432 at 8/10/10 9:51 AM:
-----------------------------------------------------------
Using <type>test-jar</type> exhibits the same exact issue in 2.2.1. The only workaround I can find is to place the test-jar dependency first - this causes the test javadoc to fail instead of the main javadoc.
was (Author: jsravn):
Using <type>test-jar</type> exhibits the same exact issue in 2.2.1. The only workaround I can find is to place the test-jar dependency first - this causes the test javadoc to fail instead of the main javadoc (which maven happily ignores).
> Incorrect classpath is used when site plugin/phase launches javadoc command
> ---------------------------------------------------------------------------
>
> Key: MSITE-432
> URL: http://jira.codehaus.org/browse/MSITE-432
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-7, 2.0.1
> Environment: Maven 2.2.1
> Reporter: Chris Tait
> Priority: Minor
> Attachments: maven-projects.zip
>
>
> When invoking the site plugin (with javadoc reporting enabled) for a project that depends on both the main artifact and the tests artifact of another project, the classpath passed to the javadoc command is incorrect.
> For example:
> Project A produces the following artifacts:
> - ProjectA-version.jar (main artifact)
> - ProjectA-version-tests.jar (test classes)
> And project B has dependencies similar to this:
> {code}<dependency>
> <groupId>...</groupId>
> <artifactId>Project1</artifactId>
> <version>...</version>
> </dependency>
> <dependency>
> <groupId>...</groupId>
> <artifactId>Project1</artifactId>
> <version>...</version>
> <classifier>tests</classifier>
> <scope>test</scope>
> </dependency>{code}
> Then only one of the jars is included in the classpath passed to the javadoc command. (Normally it seems to be the main artifact, although on one of my projects it was the tests artifact instead.) This causes lots of warnings, or for some projects causes the build to fail.
> Note that if I explicitly run the javadoc goals (i.e. "mvn javadoc:javadoc" or "mvn javadoc:test-javadoc") then the classpath is populated correctly and no errors are shown. It's only when the site plugin/phase launches it that the classpath is wrong. I've also found that the order of the dependencies within the POM file seems to make a difference in some cases.
> I've attached a zip file containing two projects to reproduce this. To run it:
> # run {{mvn install}} on project1
> # run {{mvn site}} on project2 (to see the warnings) or {{mvn javadoc:test-javadoc}}
> The warning looks like this:
> {code}[WARNING] Javadoc Warnings
> [WARNING] D:\code\EclipseWorkspaces_chris\PaymentCard\project3\src\main\java\repro3\MyClass3.java:3: cannot find symbol
> [WARNING] symbol : class MyClass1
> [WARNING] location: package repro1
> [WARNING] import repro1.MyClass1;
> [WARNING] ^{code}
--
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: (MSITE-432) Incorrect classpath is used when site
plugin/phase launches javadoc command
Posted by "James Ravn (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231600#action_231600 ]
James Ravn commented on MSITE-432:
----------------------------------
Using <type>test-jar</type> exhibits the same exact issue in 2.2.1. The only workaround I can find is to place the test-jar dependency first - the test javadoc fails instead of the main javadoc, but maven ignores it.
> Incorrect classpath is used when site plugin/phase launches javadoc command
> ---------------------------------------------------------------------------
>
> Key: MSITE-432
> URL: http://jira.codehaus.org/browse/MSITE-432
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-7, 2.0.1
> Environment: Maven 2.2.1
> Reporter: Chris Tait
> Priority: Minor
> Attachments: maven-projects.zip
>
>
> When invoking the site plugin (with javadoc reporting enabled) for a project that depends on both the main artifact and the tests artifact of another project, the classpath passed to the javadoc command is incorrect.
> For example:
> Project A produces the following artifacts:
> - ProjectA-version.jar (main artifact)
> - ProjectA-version-tests.jar (test classes)
> And project B has dependencies similar to this:
> {code}<dependency>
> <groupId>...</groupId>
> <artifactId>Project1</artifactId>
> <version>...</version>
> </dependency>
> <dependency>
> <groupId>...</groupId>
> <artifactId>Project1</artifactId>
> <version>...</version>
> <classifier>tests</classifier>
> <scope>test</scope>
> </dependency>{code}
> Then only one of the jars is included in the classpath passed to the javadoc command. (Normally it seems to be the main artifact, although on one of my projects it was the tests artifact instead.) This causes lots of warnings, or for some projects causes the build to fail.
> Note that if I explicitly run the javadoc goals (i.e. "mvn javadoc:javadoc" or "mvn javadoc:test-javadoc") then the classpath is populated correctly and no errors are shown. It's only when the site plugin/phase launches it that the classpath is wrong. I've also found that the order of the dependencies within the POM file seems to make a difference in some cases.
> I've attached a zip file containing two projects to reproduce this. To run it:
> # run {{mvn install}} on project1
> # run {{mvn site}} on project2 (to see the warnings) or {{mvn javadoc:test-javadoc}}
> The warning looks like this:
> {code}[WARNING] Javadoc Warnings
> [WARNING] D:\code\EclipseWorkspaces_chris\PaymentCard\project3\src\main\java\repro3\MyClass3.java:3: cannot find symbol
> [WARNING] symbol : class MyClass1
> [WARNING] location: package repro1
> [WARNING] import repro1.MyClass1;
> [WARNING] ^{code}
--
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: (MSITE-432) Incorrect classpath is used when site
plugin/phase launches javadoc command
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220604#action_220604 ]
Dennis Lundberg commented on MSITE-432:
---------------------------------------
This problem is not in the Site Plugin, it's in Maven core, see MNG-2045.
A workaround for that issue is to use <type>test-jar</type> instead of <classifier>tests</classifier>.
> Incorrect classpath is used when site plugin/phase launches javadoc command
> ---------------------------------------------------------------------------
>
> Key: MSITE-432
> URL: http://jira.codehaus.org/browse/MSITE-432
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-7, 2.0.1
> Environment: Maven 2.2.1
> Reporter: Chris Tait
> Priority: Minor
> Attachments: maven-projects.zip
>
>
> When invoking the site plugin (with javadoc reporting enabled) for a project that depends on both the main artifact and the tests artifact of another project, the classpath passed to the javadoc command is incorrect.
> For example:
> Project A produces the following artifacts:
> - ProjectA-version.jar (main artifact)
> - ProjectA-version-tests.jar (test classes)
> And project B has dependencies similar to this:
> {code}<dependency>
> <groupId>...</groupId>
> <artifactId>Project1</artifactId>
> <version>...</version>
> </dependency>
> <dependency>
> <groupId>...</groupId>
> <artifactId>Project1</artifactId>
> <version>...</version>
> <classifier>tests</classifier>
> <scope>test</scope>
> </dependency>{code}
> Then only one of the jars is included in the classpath passed to the javadoc command. (Normally it seems to be the main artifact, although on one of my projects it was the tests artifact instead.) This causes lots of warnings, or for some projects causes the build to fail.
> Note that if I explicitly run the javadoc goals (i.e. "mvn javadoc:javadoc" or "mvn javadoc:test-javadoc") then the classpath is populated correctly and no errors are shown. It's only when the site plugin/phase launches it that the classpath is wrong. I've also found that the order of the dependencies within the POM file seems to make a difference in some cases.
> I've attached a zip file containing two projects to reproduce this. To run it:
> # run {{mvn install}} on project1
> # run {{mvn site}} on project2 (to see the warnings) or {{mvn javadoc:test-javadoc}}
> The warning looks like this:
> {code}[WARNING] Javadoc Warnings
> [WARNING] D:\code\EclipseWorkspaces_chris\PaymentCard\project3\src\main\java\repro3\MyClass3.java:3: cannot find symbol
> [WARNING] symbol : class MyClass1
> [WARNING] location: package repro1
> [WARNING] import repro1.MyClass1;
> [WARNING] ^{code}
--
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