Affects Version/s: 1.0
Fix Version/s: None
Number of attachments :
Let's use an example: aggregating pom declares modules A (without dependencies) and B (depends on A).
Say, A module's source code was changed, and aggregating pom installing was started.
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 include some method (used by B) signature changing. At this point the aggregation installed into a repository is broken!
Expected behaviour: after installing of module A all it's dependents (inside the aggregation modules set) must be cleaned and reinstalled transitively, regardless any timestamps.
Setting priority as Critical as far as current reactor's behaviour results in inconsistent repository state.