You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2011/07/27 12:49:42 UTC

[jira] Closed: (MNG-5135) Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging

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

Benjamin Bentmann closed MNG-5135.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0.4
         Assignee: Benjamin Bentmann

Fixed in [r1151424|http://svn.apache.org/viewvc?view=revision&revision=1151424].

> Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging
> -------------------------------------------------------------------------------------------------
>
>                 Key: MNG-5135
>                 URL: https://jira.codehaus.org/browse/MNG-5135
>             Project: Maven 2 & 3
>          Issue Type: Bug
>    Affects Versions: 3.0.3
>         Environment: Maven 3.0.3
>            Reporter: Evgeny Mandrikov
>            Assignee: Benjamin Bentmann
>             Fix For: 3.0.4
>
>
> As described in SONAR-2626 : aggregator mojo, which requires dependency resolution (like "sonar:sonar" or "javadoc:aggregate-jar") is unable to resolve dependencies, when executed from command-line and build extension with custom packaging declared in sub-module, but not in parent. Declaration of extension in parent allows to workaround problem as well as downgrade to Maven 2.2.1 and execution of "mvn validate sonar:sonar".

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira