Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 315441

Summary:	Consider activation of nested team
Product:	[Tools] Objectteams	Reporter:	Stephan Herrmann <stephan.herrmann>
Component:	OTEquinox	Assignee:	Project Inbox <objectteams.otequinox-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	0.7
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Stephan Herrmann

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.