maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Evgeny Mandrikov (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MNG-5135) Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging
Date Wed, 20 Jul 2011 20:29:46 GMT

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

Evgeny Mandrikov updated MNG-5135:
----------------------------------

    Description: 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".  (was: 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 verify
sonar:sonar".)

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

        

Mime
View raw message