You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jochen Ehret (JIRA)" <ji...@codehaus.org> on 2010/03/10 09:20:55 UTC
[jira] Created: (MNG-4582) Extensions not working when defined in a
module
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
[jira] Commented: (MNG-4582) Extensions not working when defined in
a module
Posted by "Jochen Ehret (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213358#action_213358 ]
Jochen Ehret commented on MNG-4582:
-----------------------------------
I´ve attached an example project with some comments in the poms. To reproduce the error, please:
1. Run "mvn clean install" on the "quality-profiles" project.
2. Run "mvn clean install findbugs:findbugs" on the "project-build" project.
We´ve tried to add the missing dependency in the <plugin> section, but without success (Maven 2&3). It seems that the org.codehaus.mojo:findbugs-maven-plugin doesn´t evaluate additional dependencies.
Thanks again for your support!
> 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
> Attachments: exampleWithLogs.zip
>
>
> 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
[jira] Updated: (MNG-4582) Extensions not working when defined in a
module
Posted by "Jochen Ehret (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Ehret updated MNG-4582:
------------------------------
Attachment: exampleWithLogs.zip
Example project with Maven 2.2.1 and Maven 3.0-alpha-6 debug logs.
> 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
> Attachments: exampleWithLogs.zip
>
>
> 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
[jira] Commented: (MNG-4582) Extensions not working when defined in
a module
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213329#action_213329 ]
Benjamin Bentmann commented on MNG-4582:
----------------------------------------
We need some more details to analyze the issue. As a minimum, the complete debug log from Maven 3.0 that shows what's actually going on. Ideally, a complete&runnable example project.
bq. <!-- plugin that searches config files on classpath (with Plexus ResourceManager) -->
Versions of plexus-resources before 1.0-alpha-7 have bug in the resource loading that shows up in Maven 3. So updating this plugin dependency might solve the issue.
Anyways, using {{<extensions>}} here is a misuse of the element. Instead, you should declare config artifacts as dependencies of the plugin that uses them:
{code:xml}
<plugin>
<dependencies>
<!-- additional artifacts for plugin class path here -->
</dependencies>
</plugin>
{code}
> 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
[jira] Closed: (MNG-4582) Extensions not working when defined in a
module
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4582.
----------------------------------
Resolution: Duplicate
Assignee: Benjamin Bentmann
> 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
> Assignee: Benjamin Bentmann
> Priority: Minor
> Attachments: exampleWithLogs.zip
>
>
> 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