reactor doesn't reinstall untouched dependents
----------------------------------------------
Key: MREACTOR-16
URL: http://jira.codehaus.org/browse/MREACTOR-16
Project: Maven 2.x Reactor Plugin
Issue Type: Bug
Affects Versions: 1.0
Reporter: Andrew Gaydenko
Priority: Critical
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
