You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/03/26 23:23:23 UTC
[jira] Closed: (MNG-3349) reactor build order doesn't consider
plugins modules in build order
[ http://jira.codehaus.org/browse/MNG-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-3349.
----------------------------------
Resolution: Duplicate
Fix Version/s: (was: 3.0-alpha-8)
Assignee: Benjamin Bentmann
> reactor build order doesn't consider plugins modules in build order
> -------------------------------------------------------------------
>
> Key: MNG-3349
> URL: http://jira.codehaus.org/browse/MNG-3349
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Reactor and workspace
> Affects Versions: 2.0.8
> Reporter: nicolas de loof
> Assignee: Benjamin Bentmann
> Priority: Minor
>
> When a project has maven plugins as modules, and some modules use the plugin, the reactor SHOULD build the plugins before the modules that use it.
> A workaround is to declare plugins modules FIRST in parent POM <modules>
--
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