For the script way, check out http://mevenide.sourceforge.net
jeff
Svetlin Stanchev wrote:
Hi,
I am trying to enhance/replace our Ant build with Maven. But I am unable to find the answer or a good practice for a seemingly basic activity:
How can I perform a cvs checkout from scratch of multiple (>20) projects, including their project.xmls starting from the upper/top level project.xml?
I can't use the reactor as the subordinate directories are not created and populated at the very beginning.
It is my understanding per project only one module could be checked out with <repository/> (i.e. I can't specify multiple modules to be checked out). Moreover, after inspection plugin.jelly for scm:checkout-project seems to first delete the directory with the checked-out module (if any), so any kind of "bootstrapping" (creating the directories and then somehow generating or checking-out and copying the individual project.xmls) would not work either.
Is the only way to go to write a pre/postGoal ant task in the top-level maven.xml or there is something better? Why am I not able to find an example how to do this, is this considered such a rare task or I am missing something? I am really confused here.
Thanks for any help,
-- jeff bonevich mailto: [EMAIL PROTECTED]
"Any sufficiently advanced technology is indistinguishable from magic." Arthur C. Clarke
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." Rich Cook
"All programmers are playwrights and all computers are lousy actors." Unknown
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
