Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
2.1
-
None
-
all
Description
org.apache.maven.report.projectinfo.dependencies.Dependencies.mapArtifactFiles(org.apache.maven.shared.dependency.tree.DependencyNode, java.util.Map), line "anode.getArtifact().setFile( projartifact.getFile() );". The culprit is when anode.getArtifact() returns the main jar-artifact, and projartifact is the test-jar-artifact. As you can see, the main jar-artifact's file name is set to that of the test-jar-artifact.
When this happens, a subsequently executed javadoc goal composes an erroneous classpath.
Attachments
Issue Links
- is duplicated by
-
MPIR-144 Dependency report introduces corruption in classpaths for other plugins
- Closed
-
MPIR-188 Maven constructs wrong classpath element
- Closed
-
MPIR-191 Site Plugin modify Compile Plugin classpath
- Closed
- is related to
-
MPIR-223 Dependency report introduces corruption in classpaths for other plugins
- Closed
-
MJAVADOC-221 test-scoped dependencies sometimes used instead of compile-scoped if group and artifact are the same
- Closed