[MPIR-40] dependencies report no longer runs standalone

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.0
• Assignee: Edwin Punzalan
• Reporter: Brett Porter
• Created: 07/Apr/06 04:04
• Updated: 07/Apr/06 21:13
• Resolved: 07/Apr/06 21:13

Description

on maven-core, mvn project-info-reports:dependencies

java.lang.NullPointerException
at org.apache.maven.artifact.resolver.ResolutionNode.addDependencies(ResolutionNode.java:81)
at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:65)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:223)
at org.apache.maven.report.projectinfo.DependenciesReport.resolveProject(DependenciesReport.java:212)

its because it no longer does dependency resolution at the mojo level so project.getDependencyArtifacts() is null

Issue Links

• duplicates: MPIR-39 logic error in dependency resolution