Hi! Say, aggregating pom declares modules A (without dependencies) and B (depends on A). Say, I have changed source code in A and installing aggregating pom. What we shell see?
Ok, at first module A is recompiled, then module B is checked if it's source code was or was not changed, and, as far as module B sources were not touched at all, B-compiling is omited. Now imagine, those A source changings includes, say, method (used by B) signature changing. At this point, you see, the aggregation installed into a local repository is absolutely broken. Expected behaviour: after compiling A *all* it's dependents (in aggregation tree) must be *cleaned* and compiled transitively, regardless any timestamps. Agree? :-) Andrew --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
