Extensions not working when defined in a module
-----------------------------------------------
Key: MNG-4582
URL: http://jira.codehaus.org/browse/MNG-4582
Project: Maven 2 & 3
Issue Type: Bug
Components: Class Loading
Affects Versions: 3.0-alpha-6
Reporter: Jochen Ehret
Priority: Minor
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?
--
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
