Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 1.4.1
-
Fix Version/s: None
-
Labels:None
-
Environment:maven 1.1-beta 1 / beta 2
-
Testcase included:yes
Description
This issue isn't in the multiproject plugin but in the core (MAVEN-1691) . I create it to avoid others users to search for this problem.
Let's imagine we have the following projects :
myProject
| -mySubProjectA |
| -mySubProjectA.1 |
|---|
| -mySubProjectA.2 |
| -mySubProjectB |
| -mySubProjectB.1 |
| -mySubProjectB.2 |
You create a custom goal in myProject (myGoal) which calls the goal goalLevel1 in each direct subproject (*/project.xml)
In mySubProjectA and mySubProjectB you do the same and call another goal in subprojects (goalLevel2)
Here is what maven do :
myProject => myGoal OK
| -mySubProjectA => goalLevel1 OK |
| -mySubProjectA.1 => goalLevel2 OK |
|---|
| -mySubProjectA.2 => goalLevel2 OK |
| -mySubProjectB => goalLevel2 KO |
| -mySubProjectB.1 |
| -mySubProjectB.2 |
The multiproject fails because it forgot that in mySubProjectB, it should call goalLevel1.
The problem is when the second multiproject is called, it replace the value of the variable goal for the project myProject.
A testcase is given in MAVEN-1691.
Issue Links
- depends upon
-
MAVEN-1691
Variable scope problem
-