> Solution 1 is as Jamie suggested: have CC monitor trunk. To do this, > however, you'll need to have a project.xml in the trunk directory for > the sole purpose of hooking it up to CruiseControl. The trunk project > could then call through to the multiproject when it actually builds.
I am ok with this approach. the only part I'm not sure how to do is the last part.. how does the project.xml call the real multiproject's project.xml and invoke my goals (scm:update, clean, multiproject:deploy, multiproject:site, site:deploy)? Thanks a lot for the help, I've seen these types of questions raised a few times in the CC & Maven mailing lists but I haven't been able to find an answer. I think it'd be great to get the details worked out. :) -michael -- This E-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return E-mail. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
