I have a pre-goal of a cvs checkout for a subproject , that uses the
was-40 plugin.My top level maven.xml file looks as follow
<project default="support-build-all" xmlns:j="jelly:core"
xmlns:m="jelly:maven">
<preGoal name="support-build-all">
<j:set var="maven.scm.cvs.module">Support_Persistence</j:set>
<attainGoal name="scm:cvs-checkout-project"/>
</preGoal>
<goal name="support-build-all">
<m:reactor basedir="${basedir}"
includes="*/project.xml"
goals="support-build-all"
banner="Building Project"
ignoreFailures="false"/>
</goal>
</project>
The Support_Persistence is a sub-project sitting directly under the top
level project called Support i.e
/Support/Support_Persistence.Soupport_Pesristence has the following maven.xml file :
<project default="support-build-all" xmlns:j="jelly:core"
xmlns:m="jelly:maven">
<goal name="support-build-all">
<attainGoal name="ejb:install"/>
<attainGoal name="site:generate"/>
</goal>
</project>
When I run maven from the top level project Support , the cvs checkout
pregoal is being run twice , and then the was-40 plugin is also run
twice such that the deploy code is generated twice.When the check-out
pregoal is executed for the second time it checks out a copy of the
Support_Persistence subproject into the already checked-out
Support_Persistence sub-project , such that I end up with a directory structure that
looks like as shown below
/Support/Support_Persistence (with all the project files , etc)
and /Support/Support_Persistence/Support_Persistence (also with all
the project files)
When I comment out the Reactor call , the check out works fine(i.e
there is no duplicate subproject).
I've spend some time trying to fix this without success
jeff mutonho
---------------------------------
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
