Bug #1492
Updated by Henning Blohm over 11 years ago
There are currently numerous problems with includes:
h2. Problem: No good dependency and invalidation handling
See #1481.
h2. Unnoticable resource updates
See #1491
h2. No decent development model
Anything that relies on includes as extension model, should be development enabled. I.e. assuming a Java component A, relies on Java component B via includes and B relies on C the same way, all the following conditions should be met:
* Resolving A via eclipsoid should have includes resolved transitively (i.e. it should provide B,C included)
* B may need A for compilation. So it should be ok to have a ref from B to A. That however leads to a cycle today.
See [[Revisiting_includes_for_2_3]].