Nigel,
If the project you are dependent upon is also being built by CruiseControl,
you can add a <buildstatus> element inside the modificationset like so:
<buildstatus logdir="/usr/local/cruisecontrol/logs/dependentProject">
</buildstatus>
This basically states that anytime a new build of dependentProject occurs, build the
project even if there are no changes in cvs.
What this won't do is always build dependentProject first. That is, if you make
changes in both projects, there's no guarantee that dependentProject
goes first. I'd like to see that feature
added somehow.
-wr
P.S. This topic probably makes more sense on the CruiseControl mailing list.
Nigel Magnay <[EMAIL PROTECTED]> on 10/07/2004 06:05:58 AM
Please respond to "Maven Users List" <[EMAIL PROTECTED]>; Please
respond to Nigel Magnay <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
cc: (bcc: Winston Rast/Jeppesen/TMC)
Subject: CruiseControl, Maven, modificationsets
(Embedded image moved to file: pic24464.jpg)
Hi people
We're using CruiseControl and Maven quite happily for individual
project builds and larger 'continuous integration' type stuff.
Cruisecontrol gets launched with the cvs modificationset detecting
whether there have been any changes to a part of the cvs repo relevant
to that project.
It would be very useful to have an additional modificationset that
used the maven dependency list in order to find out if any of the
dependencies has been modified in the local (or maybe remote) repo.
I think it might be relatively easy to call out to maven to get it to
show the timestamp for all the dependencies that it is going to use,
and compare them to a previously stored list.
Has anyone already written anything like this?
---------------------------------------------------------------------
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]
