Thanks for this great trick; it has worked well for us with version 2.7.3 of CruiseControl, but I’m having difficulties with version 2.8.2. Have you tried this with 2.8.2? I’m getting a “java.lang.VerifyError” being thrown somewhere inside the constructor to XmlConfigManager. We’re using Java 6 on linux.

Ouch. I think it’s the CVS ModificationSet in CruiseControl. It has no such entity as the repository revision number in SVN, so it uses the working copy. Sorry to put you crook.

There’s one thing that I can’t figure out from your config.xml. If the bootstrapper updates the local copy of a project every time, then the modificationset will never find a change, thus never trigger the build. It happened to me.

Since requireModification defaults to “true”, CruiseControl will never build that project because it’s always up to date Btw. I use CVS, and the solution was just to remove the bootstrapper.

–
Alex

Directory layout: yes. I think I assumed the default layout from the distribution (but on my old linux laptop, I think it was rooted somewhere in /var/tmp/cruisecontrol-2.7 or sommat)

Rebuilds? I should have used the <uptodate> task so that the validator didn't get rebuilt every time.

The config file? You can pass any file you like to the config attribute of the validate element. That is the file that will be validated.

It should be pretty straightforward to map to your own config. I believe that you'll need to tell the validator (at runtime) where the cruisecontrol.jar file is, and where the config file under test is.

* It looks like you are assuming a different directory layout here than that illustrated in the “Keep Your Dependencies to yourself” post, is that correct? I think it is assuming a /project directory directly under the cc installation dir?

* Will this rebuild the cruise-validator.jar again and again or just once? (I think I'm getting thrown off because the cruise-validator is just another project, rather than a .jar file manually added to cruise control)

* When developers want to modify the cruise control config file, do they modify the one in the cruise-validator project (set via the "config" property in build-library)? Or is that config.xml file merely meant to be <include.project>ed into my main config file?

Sorry if I've missed something, I'm attempting to follow what you've done here and map it to the crazy layout and config files I've inherited at the same time.

What are you trying to include?