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

["John Casey (JIRA)" <ji...@codehaus.org>]

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

John Casey commented on MNG-1323:
---------------------------------

This, along with different plugin versions used in different POMs within a single multimodule build, is something I addressed for trunk (2.1). To make it work, I had to setup a realm manager to track plugins using a key that's based on groupId:artifactId:version, PLUS a hash of the dependency-id's it uses. This allows naming of the plugin realm accordingly, and helps to retrieve the correct realm for use when a plugin is executed.

The problem is, it requires use of the new lookupRealm(..) functionality of later plexus-container-default releases (> ~1.0-alpha-16, IIRC), and upgrading Maven 2.0.x to a compatible plexus version may well break other things.

It may be that this issue cannot be resolved in a satisfactory manner until 2.1 is released. The good news is, it should work in the first alpha of 2.1.

> Plugin extensions (dependencies) not resolved in reactor build
> --------------------------------------------------------------
>
>                 Key: MNG-1323
>                 URL: http://jira.codehaus.org/browse/MNG-1323
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 2.0
>            Reporter: Kenney Westerhof
>             Fix For: 2.0.10
>
>         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