You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Evgeny Mandrikov (JIRA)" <ji...@codehaus.org> on 2011/07/20 22:25:42 UTC
[jira] Created: (MNG-5135) Regression: in some cases aggregator
mojo is unable to resolve dependencies with custom packaging
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 verify sonar:sonar".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5135) Regression: in some cases aggregator
mojo is unable to resolve dependencies with custom packaging
Posted by "Christian Pesch (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274482#comment-274482 ]
Christian Pesch commented on MNG-5135:
--------------------------------------
Interesting question. I've found a post from April:
http://maven.40175.n5.nabble.com/3-0-4-release-td4311795.html
> 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
[jira] Closed: (MNG-5135) Regression: in some cases aggregator mojo
is unable to resolve dependencies with custom packaging
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MNG-5135) Regression: in some cases aggregator
mojo is unable to resolve dependencies with custom packaging
Posted by "Evgeny Mandrikov (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MNG-5135) Regression: in some cases aggregator
mojo is unable to resolve dependencies with custom packaging
Posted by "Evgeny Mandrikov (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274373#comment-274373 ]
Evgeny Mandrikov commented on MNG-5135:
---------------------------------------
Benjamin, thank you! BTW, is there any plans for release of 3.0.4?
> 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