[MNG-4582] Extensions not working when defined in a module

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 3.0-alpha-6
• Component/s: Class Loading
• Assignee: Benjamin Bentmann
• Reporter: Jochen Ehret
• Created: 10/Mar/10 02:20
• Updated: 10/Mar/10 12:12
• Resolved: 10/Mar/10 12:12

Description

We want to use Maven Extensions so we can easily look up configuration files. This is our project configuration:

build-project (contains only list of modules):

<modules>
<module>parent-project</module>
<module>subproject1</module>
<!-- more modules -->
</modules>

parent-project (contains only configurations, has no declared <parent> project):

<build>
<extensions>
<extension>
<!-- artifact with config files -->
</extension>
</extensions>
<plugins>
<plugin>
<!-- plugin that searches config files on classpath (with Plexus ResourceManager) -->
</plugin>
</plugin>
</build>

subproject1 (has parent-project as <parent>, executes plugin)

With maven-2.2.1 the config files are correctly loaded and available on the classpath. With maven-3.0-alpha-6, the config files are not on the classpath.

If we move the extension up into the "build-project", the config files are available again, but we would like to keep configurations out of the build-project.

Can you please fix the extension classpath loading?

Issue Links

• duplicates: MNG-4580 Plugin dependencies for module ignored when building from aggregator project using direct plugin invocation