You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hannes Schmidt (JIRA)" <ji...@codehaus.org> on 2011/04/08 00:27:23 UTC

[jira] Commented: (MNG-1323) Plugin extensions (dependencies) not resolved in reactor build

    [ http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262896#action_262896 ] 

Hannes Schmidt commented on MNG-1323:
-------------------------------------

Can this please be backported to 2.2.x. I've been using Maven since 2005 and this thing has been bugging me once every so often with enough time in between for my brain to garbage collect my awareness of this bug. So I basically spend a few hours every year hunting plugin dependency problems with reactor builds and ultimately land on this page.

BTW, my workaround is to collect all plugin dependencies in the pluginManagement section of a parent pom that's common to all modules.

> Plugin extensions (dependencies) not resolved in reactor build
> --------------------------------------------------------------
>
>                 Key: MNG-1323
>                 URL: http://jira.codehaus.org/browse/MNG-1323
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 2.0
>            Reporter: Kenney Westerhof
>             Fix For: 3.0-alpha-1
>
>         Attachments: MNG-1323-components-2.0.x.diff, MNG-1323-core-integration-testing-2.diff, MNG-1323-core-integration-testing.diff, MNG-1323-core-integration-tests-3.diff, MNG-1323-core-integration-tests.diff, MNG1323-maven-core-2.1.diff, two-antruns.zip
>
>
> I've added a dependency on an Ant Task in project/build/plugins/plugin[artifactId='maven-antrun-plugin']/dependencies/ and run that anttask using the antrun plugin.
> When run from the project dir itself it runs fine.
> When running from the root of the project tree (reactor build, project one level below root),
> antrun bails out because the taskdef can't be found (not on classpath).
> It looks like the dependency isn't resolved, or not added to the plugins' classrealm.

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