Maven 1.x Multi-Project Plugin

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.4.1
• Fix Version/s: None
• Component/s: None
• Labels:

  None
• Environment:

  WinXP maven-1.0.2

I have found a strange bug in the combination of the cactus-plugin 1.7
and the multiproject-plugin 1.4.1.

When using the cactus goal in the sub-project, everything works fine
here is an extract of the subproject maven.xml :

<goal name="project:clean">
<attainGoal name="clean"/>
</goal>

<goal name="project:snapshot">
<attainGoal name="test"/>
<attainGoal name="cactus"/>
</goal>

<goal name="project:clean-snapshot">
<attainGoal name="project:clean"/>
<attainGoal name="project:snapshot"/>
</goal>

<goal name="project:dist-src">
<attainGoal name="project:clean-snapshot"/>
<attainGoal name="site"/>
<attainGoal name="dist:build-src"/>
</goal>

project:dist-src is the goal i call in the subproject directory.

when i call the same goal (using the multiproject plugin from the
englober project)
it doesn't works.

here is an extract of the project englober maven.xml

<goal name="project:multi-dist-src">
<j:set var="goal" value="project:dist-src"/>
<attainGoal name="multiproject:goal"/>
</goal>

and project:multi-dist-src is the goal i call from the project englober
directory.

I have attached the console results of both the only local working goal
(war.txt) and the englober log (englober.txt)

I have also snipped the logs for more clarity.

1. 

   englober.txt

   23/Jun/05 9:17 AM

   19 kB

   larafale

2. 

   war.txt

   23/Jun/05 9:17 AM

   6 kB

   larafale

• Assignee:

  Unassigned

  Reporter:

  Raphaël Piéroni

• Created:

  23/Jun/05 9:17 AM

  Updated:

  25/May/07 8:32 AM