Allow One Plan To Be Based On Multiple CVS Modules

Please allow multiple CVS modules to be listed as the module for a CVS-based plan. The use-case for this is CVS repository with code broken into multiple modules, where one particular component wants to be tested but other modules (such as 'lib') are required.

Our CVS repository, for example, has top-level modules named: core, gui, lib, tests, and components. We also have an amper-module called 'limewire' that has some additional top-level data and then references those. For Bamboo, we have three plans: LW-COMPILATION, LW-NIGHTLY, and LW-COMPONENTS. The compilation plan just checks that all the code compiles and runs whenever anything in the 'limewire' module changes. We can't run all the tests all the time because they take too long to run. The nightly plan runs every night and runs the full test suite. The components build is where the problem lies.

The components module requires the lib module is checked out as a sibling, and references those files. To workaround this, I created an amper-module that gets both components & lib. It would be nice if this workaround were not required, and Bamboo would allow multiple modules per plan.