I'm not sure the steps are quite right there.. The way I understand CC is that CC handles the checkout of the code instead of Maven. The reason is that that is how CC knows if any changes have been made, which is then used to decide if it should actually trigger a build. Therefore you need to doublec cehck CC's support for VSS, which is there.
If you are using something like the AlwaysBuild (my contrib ;-) ) or the Timed build, then it doesn't matter if CC or Maven dos the check out, use whichever you prefer. Eric > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Friday, December 03, 2004 9:57 PM > To: Maven Users List > Subject: Re: Anyone really doing continuous integration with Maven? > > > Yes. > > In maven.xml, define: > <goal name="update-project"> > ... do your VSS update, possibly with Ant ... > </goal> > > If you call that goal first, you're all set. > > I think I have a patch sitting around for VSS support in SCM - let me > see if I can get to that by the end of the year :) > > - Brett > > > On Fri, 3 Dec 2004 15:46:43 -0500, Poppe, Troy > <[EMAIL PROTECTED]> wrote: > > > > I'm revisiting a previous attempt to setup CruiseControl thanks > to your post > > here... > > > > I'm having a difficult time understanding the Maven builder.... > It looks like > > the Ant builder wants you to write a delegating build script > which goes and gets > > all the source from your source repository, and then executes > the appropriate > > build script from there. (This could be a call to maven...) > My assumption would > > be that the Maven builder would do exactly the same thing... > Get some code out of > > your SCM and run some goals. > > > > My confusion comes from the fact that our SCM is currently > VSS... (*sigh*).... So > > I really cant use Maven to retrieve my source from VSS... So > should I skip the > > Maven builder in CruiseControl until I get to a SCM that is > supported by Maven? > > Is there anyway to use the Maven builder with my code being in VSS? > > > > > > > > T > > > > -----Original Message----- > > From: STRAYER, JON (SBCSI) [mailto:[EMAIL PROTECTED] > > Sent: Friday, December 03, 2004 9:44 AM > > To: Maven Users List > > Subject: RE: Anyone really doing continuous integration with Maven? > > > > > I have about 15 projects and a master POM for all of them. I > > > use maven to build the individual projects as well as the > > > integrated web site. When Maven does this multiproject build, > > > it uses the current development branch for the project that > > > it is building, but the current stated _dependencies_, not > > > from the source, for each dependency. > > > > > > That is, Maven is NOT doing continuous integration in a > > > multiproject build. For example, Maven does not build the > > > dependencies from the most current source for the stated > > > revision of that dependency. > > > > > > So, my question is: Is anyone doing continuous integration > > > builds using Maven and how? > > > > We are, via CruiseControl. We have 27 projects that all share > a master POM (17 > > applications & 10 libraries). Any time someone checks in code > CruiseControl > > checks it back out, builds the project and dropps a SNAPSHOT jar in the > > repository. > > > > As of version 2.2 you can have CruiseControl check a project's > POM for SNAPSHOT > > dependencies and rebuild when their timestamp changes. So, > anytime a library > > changes any project that uses it is also rebuilt (and tested). > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
