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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 3.0-alpha-1
• Component/s: Plugins and Lifecycle
• Assignee: Unassigned
• Reporter: Kenney Westerhof
• Created: 25/Oct/05 16:50
• Updated: 06/Apr/15 00:41
• Resolved: 29/Nov/08 00:51

Description

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.

Issue Links

• is depended upon by: MPLUGIN-37 parent with multi-type mojo children does not build ant mojo
• is duplicated by: MANTRUN-52 plugin dependencies seem to get lost when using the plugin multiple times
• is duplicated by: MANTRUN-51 Problems with multiple antrun declarations in multiproject
• is duplicated by: MANTRUN-61 Classloader issue with ant optional tasks in a hierarchical structure
• is duplicated by: MANTRUN-63 ant classpath resolves incorrectly if project is invoked as part of multi-project builds
• is duplicated by: MNG-1949 project-level plugin dependencies not handled correctly in multimodule builds
• is duplicated by: MNG-2946 Module-by-Profile seems to break plugin dependencies
• is duplicated by: MNG-3950 With multiple modules using the same plugin later invocations of the plugin are not initialized
• is duplicated by: MNG-4178 Plugin dependency not always included to classpath
• is duplicated by: MNG-5290 Plugin extensions (dependencies) not resolved in reactor build
• is related to: MASSEMBLY-468 Sharing assembly descriptor across sub modules does not work if parent defines assembly and submodule want to add own assembly
• is related to: MNG-1949 project-level plugin dependencies not handled correctly in multimodule builds
• relates to: MASSEMBLY-233 Custom ContainerDescriptorHandler integration tests don't work in Maven 2.0.7
• relates to: MNG-1911 Building plugins with extensions in a reactor fails
• relates to: MNG-3284 Cached plugins are used, even when the specifically declared
• relates to: MANTRUN-106 Maven dependency bug can lead to very confusing failures