[jira] (MNG-4851) MavenProject.getDependencyArtifacts() returns null when executed from custom lifecycle

["Michael Osipov (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MNG-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated MNG-4851:
--------------------------------

    Affects Version/s:     (was: 2.2.x (to be reviewed))

> MavenProject.getDependencyArtifacts() returns null when executed from custom lifecycle
> --------------------------------------------------------------------------------------
>
>                 Key: MNG-4851
>                 URL: https://jira.codehaus.org/browse/MNG-4851
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>         Environment: Ubuntu Linux 10.04, kernel version 2.6.35-5-generic-pae #6-Ubuntu SMP Tue Jun 22 08:21:56 UTC 2010 i686 GNU/Linux
>            Reporter: Michael Cramer
>         Attachments: maven-testbug-plugin.zip
>
>
> When executing a plugin mojo, there seems to be a case when the call to MavenProject.getDependencyArtifacts() returns null when executed from a mojo that forks a custom lifecycle execution.  The method works fine when the mojo is invoked directly or from pom.  Compare the two cases in the included sample plugin...
> mvn test:maven-testbug-plugin:testbug1 
> mvn test:maven-testbug-plugin:testbug2
> Executing the first will result in the dependencies being printed.  Executing the second results in a null pointer exception.  But all the second really does is call the first, unless I'm misunderstanding something...



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)