Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.3, 2.3.1
-
Fix Version/s: 2.4
-
Component/s: dependencies
-
Labels:None
-
Testcase included:yes
-
Number of attachments :
Description
MPIR-144 shows up again per Neil Hartner comments. Creating this new issue
====
This issue has reappeared in 2.3.1. I'm attaching an updated version of the zipped maven project that reproduces this issue. You can change which version of MPIR plugin to use with -Dmpir-version. For example:
mvn clean install site:site -Dmpir-version=2.3.1
2.1, 2.3 and 2.3.1 will fail
2.1.1 and 2.2 will succeed
Issue Links
- is depended upon by
-
MJAVADOC-279
Javadoc plugin doesn't set dependencies correctly when pom uses classifiers
-
- is related to
-
MPIR-158
Artifact ###### has no file error.
-
- relates to
-
MJAVADOC-302
Classpath cleared after maven-javadoc-plugin:javadoc
-
-
MPIR-146
org.apache.maven.report.projectinfo.dependencies.Dependencies.mapArtifactFiles(DependencyNode, Map) wreaks havoc upon artifacts file names
-
-
MPIR-144
Dependency report introduces corruption in classpaths for other plugins
-
fixed in r1098179, with an IT to ensure the bug won't reappear