I don't normally cross-post messages, but I'm not certain which list is the best for this question. If this breaks an etiquette rule, I apologize.
I have a handful of maven2 multi-module projects that I have configured to continuously integrate within CruiseControl. Currently I have each submodule being built as a separate project within the CC configuration file. Is this the proper way to configure submodules? I don't want to rebuild every submodule if only one changes. However, I've found that breaking the modules up tends to cause many failed builds if I've made changes to different areas of the code base at the same time. For example, if I change code in a submodule within project A, and modify code that depends on it in project B, CC will sometimes try to rebuild project B first. I'm using the maven snapshot dependency plugin to cascade changes, but I'd really like for CC to be able to trace up the dependency hierarchy to know that the module in project A has changes as well and build it before the module in project B. Thanks, Chris Schmidt
