You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Edwin Punzalan (JIRA)" <ji...@codehaus.org> on 2006/04/08 04:14:48 UTC

[jira] Closed: (MPIR-40) dependencies report no longer runs standalone

     [ http://jira.codehaus.org/browse/MPIR-40?page=all ]
     
Edwin Punzalan closed MPIR-40:
------------------------------

     Assign To: Edwin Punzalan
    Resolution: Fixed

> dependencies report no longer runs standalone
> ---------------------------------------------
>
>          Key: MPIR-40
>          URL: http://jira.codehaus.org/browse/MPIR-40
>      Project: Maven 2.x Project Info Reports Plugin
>         Type: Bug

>     Versions: 2.0
>     Reporter: Brett Porter
>     Assignee: Edwin Punzalan
>      Fix For: 2.0

>
>
> 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

-- 
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