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/01/06 14:42:56 UTC
[jira] Closed: (MNG-2135) multi-project build that creates it's own
plugins needs bootstrapping
[ http://jira.codehaus.org/browse/MNG-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-2135.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.0-alpha-7)
3.0-alpha-3
Assignee: Benjamin Bentmann
> multi-project build that creates it's own plugins needs bootstrapping
> ---------------------------------------------------------------------
>
> Key: MNG-2135
> URL: http://jira.codehaus.org/browse/MNG-2135
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.2
> Reporter: Frank Cornelis
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-3
>
>
> I have a multi-project build. Some of the artifacts are maven-plugins. Other artifacts depends on these plugins. For some reason the current Maven2 is not correctly doing the dependency check before building to see whether the artifacts in the multi-project build depend on other maven-plugin artifacts within the same multi-project build.
> For now I solved the issue by using a second parent pom to bootstrap the build. This bootstrap parent pom is creating all the plugins. Afterwards, I can use my normal parent pom to build all artifacts.
> It would be nice that Maven2 could do the 'bootstrap build' himself.
--
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