You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lammert Westerhoff (JIRA)" <ji...@codehaus.org> on 2008/10/22 13:54:20 UTC
[jira] Created: (MNG-3801) Plugin dependencies for module ignored
when building from aggregated project
Plugin dependencies for module ignored when building from aggregated project
----------------------------------------------------------------------------
Key: MNG-3801
URL: http://jira.codehaus.org/browse/MNG-3801
Project: Maven 2
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.0.9
Reporter: Lammert Westerhoff
I have defined a plugin in the build->plugins section in my pom. The plugin needs a plugin dependency to get a certain resource during execution (it is the maven-assembly-plugin that needs a custom descriptorRef that is located in another jar). When building the project from the module directory, everything works fine. But when I build the project from the parent aggregation from the module, it seems to ignore the plugin dependency of the plugin defined in the module and fails with an error that it cannot find my resource (in this case it does not find my assembly descriptor).
A work around is to also put the plugin dependency in the parent aggregation pom. The execution and configuration part can stay in the module pom. Now the module plugin will get the plugin dependency for this plugin from the parent. However, it also needs to stay in the module in case not building from the aggregation.
--
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-3801) Plugin dependencies for module ignored
when building from aggregated project
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-3801.
-----------------------------
Assignee: Brett Porter
Resolution: Duplicate
> Plugin dependencies for module ignored when building from aggregated project
> ----------------------------------------------------------------------------
>
> Key: MNG-3801
> URL: http://jira.codehaus.org/browse/MNG-3801
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.9
> Reporter: Lammert Westerhoff
> Assignee: Brett Porter
>
> I have defined a plugin in the build->plugins section in my pom. The plugin needs a plugin dependency to get a certain resource during execution (it is the maven-assembly-plugin that needs a custom descriptorRef that is located in another jar). When building the project from the module directory, everything works fine. But when I build the project from the parent aggregation from the module, it seems to ignore the plugin dependency of the plugin defined in the module and fails with an error that it cannot find my resource (in this case it does not find my assembly descriptor).
> A work around is to also put the plugin dependency in the parent aggregation pom. The execution and configuration part can stay in the module pom. Now the module plugin will get the plugin dependency for this plugin from the parent. However, it also needs to stay in the module in case not building from the aggregation.
--
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