Thanks for the tip. That worked great.
My next concern is having the output from Maven show up in the CC "Build Results" tab. It looks like Ant logs for CC to a file while this isn't happening for Maven? The downside is that I can see the output in the cmd shell I'm running CC from, but if the build won't compile, other developers can't see the reason from the CC results page.
Any ideas?
Thanks, Guy
Nicolas Chalumeau wrote:
Call first the update of your project I your list of goal to attain
<schedule interval="30"> <maven goal="scm:update-project|clean|test" projectfile="project.xml" mavenscript="c:/maven/bin/maven"> </maven> </schedule>
Nicolas
On Tue, 18 Jan 2005 08:28:20 -0700, Guy Davis <[EMAIL PROTECTED]> wrote:
Hello,
I'm trying to get CruiseControl working for our Maven-controlled build. If I set the CC config.xml to call have a <maven> entry within the <schedule> element with a target of site, then the build happens but the checked out tree (via Subversion) isn't updated first.
Is there anyone else using Maven, CruiseControl and Subversion. I can get things going with CruiseControl calling a small Ant script which updates the tree, then calls Maven with an exec. This seems like a bit of a hack to me though. Are there better approaches that don't involve using an Ant intermediary?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
