Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.2
-
Fix Version/s: 3.0-alpha-3
-
Component/s: Dependencies
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
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.
Issue Links
- is duplicated by
-
MNG-1883
it plugin not picking up the plugin being built (goes to the local repo instead)
-
-
MNG-3349
reactor build order doesn't consider plugins modules in build order
-
- is related to
-
MNG-1088
Plugins built and used within the same multiproject build fail unless lifecycle phase is compile or later
-
-
MNG-870
Make plugin discovery reactor aware
-
- relates to
-
MNG-4081
Subtle case: Avoid resolving artifacts from outside the reactor for plugins and extensions whose projects are inside the reactor
-
Validate this is fixed.