I'm concerned that the cruisecontrol build is not in sync with HEAD. or maybe I just don't understand how it works.
More than a week ago I changed the build.xml to separate the JCR tests into their own junit task. This (temporarily) solves the out of memory problem (what is really going on behind the test failures). When I run today's build.xml locally I get the problem with incompat's with the commons-collections; not the out of memory error.
I do not see this same problem with the QA build. This has me concerned that something is out of sync with their process.
Also, should head be building 3.2 beta 1 artifacts? or SNAPSHOT..IMO it is incorrectly labeling the artifacts as 3.1.
i'm going to refocus on fixing the cruise control builds after the mavenization.
QA is currently too overloaded.
But the point you raise is an interesting one. I'll inform with QA on what the normal delay should be and what the causes could be of the longer delay that we're seeing.