[cross-project-issues-dev] Object Teams joining Indigo - Discussing non-

[Stephan Herrmann <stephan@xxxxxxxxxxxxxxx>]

Hi All,

The Object Teams Project is preparing to join Indigo. When reading the
rules for simulateous releases [1], it feels that Object Teams might
set a precendent in several regards:
 - we use a patch feature to replace the jdt.core with a compatible,
   extended variant.
 - we use Equinox adaptor hooks for byte code weaving into other
   plug-ins.
 - we use p2.inf to modify config.ini and eclipse.ini
Each of these items, when used in uncontrolled ways, might be seen
as violating the "API" and "Do No Harm" rules.

Object Teams has a tradition of *openness* regarding non-standard
ways of component composition (see [2] for a conceptual discussion
of "gradual encapsulation"). We acknowledge the conflict between
*strict rules* for component composition and a desire for more *flexibility*
in order to support more unanticipated compositions.
A central idea behind "gradual encapsulation" is to support both sides
of the spectrum and provide the user with the necessary information
and tools for deciding whether or not a specific usage of one of the
above mechanisms should be accepted or not.

Very much in this vein I opened bug 316702 [3], where I try to put all (?)
relevant mechanisms into context. I'd appreciate your comments on 
that bug, because I believe this is an important issue for the Eclipse
ecosystem in general, not just regarding Object Teams.

best,
Stephan

[1] http://eclipse.org/helios/planning/EclipseSimultaneousRelease.php
[2] http://www.jot.fm/issues/issue_2008_12/article3.pdf
[3] https://bugs.eclipse.org/316702 "More feedback on what's installing"