Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315441 - Consider activation of nested team
Summary: Consider activation of nested team
Status: NEW
Alias: None
Product: Objectteams
Classification: Tools
Component: OTEquinox (show other bugs)
Version: 0.7   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-02 14:08 EDT by Stephan Herrmann CLA
Modified: 2010-06-02 14:08 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Herrmann CLA 2010-06-02 14:08:56 EDT
Since aspectBindings can be defined for nested teams, too,
it should be considered, whether activation of nested teams should
also be supported. This is a bit tricky because instantiating a nested team 
can only be performed on behalf of an instance of the outer team.

If the enclosing team has activation="NONE" it must be enforced
that also the nested team has activation="NONE" (in UI and runtime).

If enclosing and nested teams are bound to different base plug-ins,
the order of instantiating and activating both teams can become tricky, too,
because team instantiation is connected to the activation of its base plug-in.