Let's attempt to learn as much as possible on each run. And that means using the newest build available.
I do see one possible problem we could face
From above let project A and project B both depend on Project Z
Project Z makes a change and project B makes a change to match.
Now since project A is not building Project C will use the old version of Project A with new version of Project B. If they are incompatible Project C will see the error not Project A. But we still learn something as early as possible just not in the desired place.
If the cascading errors/warnings idea from another RT thread, or the list of all changes idea from another RT thread still, were implemented too, this wouldn't be an issue. We would end up with something like:
Error: 'A' failed to build because of Exception dddd [EMAIL PROTECTED], possible causes:
'A':src/java/org/apache/a/foo.java changes to lines 34, 36, 144 [EMAIL PROTECTED]
'Z':/src/java/org/apache/z/bar.java changes to lines 244-268 [EMAIL PROTECTED]
Warning: 'C' requires failed prerequisite 'A' - using build from 2004-03-27 instead
Error: 'C' failed to build because of Exception ffff [EMAIL PROTECTED], possible causes:
'C':/src/java/org/apache/c/baz.java changes to lines 640-699 [EMAIL PROTECTED]
'A':src/java/org/apache/a/foo.java (inherited from 'A') changes to lines 34, 36, 144 [EMAIL PROTECTED]
'Z':/src/java/org/apache/z/bar.java (inherited from 'A') changes to lines 244-268 [EMAIL PROTECTED]
-- Michael
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
