Rupert Smith wrote:
How about this. Instead of putting these JMS+Qpid java tests under trunk/qpidtests (or jmstests or whatever), lets put them in a module under trunk/qpid/java/integrationtests (or jmstests or how about 'regressiontests'?). Trunk will be the definitive source for these non-version specific, non-branch specific tests, they will be pulled onto the M2/2.1 or other branches by setting up an svn:external onto trunk. That way they will always be the same accross all branches, and there will be no need to start putting stuff outside of trunk/qpid.
Does this mean that when you modify the tests you need to build all the branches to make sure you didn't break anything?
--Rafael
