Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-beta-3
-
Fix Version/s: 2.0.1
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
DependenciesReport.java, inside getMavenProjectFromRepository( Artifact artifact, ArtifactRepository localRepository )
projectArtifact.file is always null, and when calling mavenProjectBuilder.buildFromRepository causes
java.lang.NullPointerException
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:82)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63)
at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:377)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:343)
at org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.getMavenProjectFromRepository(DependenciesReport.java:373)
at org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.renderBody(DependenciesReport.java:297)
at org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
I've made a quick fix ignoring system dependencies, not sure if we want to change it
Inside renderBody
if ( Artifact.SCOPE_SYSTEM.equals( artifact.getScope() ) )
Attachments
Issue Links
| This issue is duplicated by: | ||||
| MNG-2353 | mvn site:site fails generating the dependencies if the MNG-806 fix is present |
|
|
|
| MPIR-23 | Crash when processing system-scoped dependencies |
|
|
|
| MPIR-24 | Possible NPE in DefaultArtifactResolver |
|
|
|
| MPIR-37 | Dependency report fails on system-scope dependencies |
|
|
|
| MSITE-125 | NullPointerException generating the "Dependencies" report if using system scope dependencies |
|
|
|
| MNG-2150 | Dependencies crash with NullPointerException on system dependencies |
|
|
|
| SUREFIRE-277 | report fails with a jar of "system" scope |
|
|
|
| This issue is related to: | ||||
| MNGECLIPSE-157 | Runtime exceptions in embedder should be caught and logged by the plugin. |
|
|
|
artifactProject = getMavenProjectFromRepository(...) is only used to get url and description.
So, the report puts these informations in the dependencies table.
Maybe, we could add the SCOPE_SYSTEM test and thus, skipping the display of url and description.