I found this on eclipse.org: http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_2.html#JDT
Split refactoring. Refactoring currently relies on a closed world assumption. This means that all of the code to be refactored must be available in the workspace when the refactoring is triggered. However for large distributed teams, the closed world approach isn't really feasible. The same is true for clients which use binary versions of libraries where API changes from one version to another. In 3.2 the closed world assumptions will be relaxed in such a way that a refactoring executed in workspace A can be "reapplied" on workspace B to refactor any remaining references to the refactored element. [JDT Core/UI] (106207) [Theme: Scaling Up].
Eclipse 3.2 is announced to be release in late june (during the next days
This should make it possible for us to change a lot of things without worrying about people using the new version to be f**ked up
So we are free to reform/improve the package hierarchy of xith.