Revise launch configurations for OT/J

[stephan]

Instead of providing new launch configuration types for all kinds of OT/J programs (Java Application, JUnit, Eclipse Application ..) we should perhaps just offer a check box for all of those launch types for enabling OT/J.

[mosconi]

Additionally, we could provide a consistent Team Activation tab for the different launch types.

[stephan]

Initial implementation is in r18844:

No longer need to create launch configurations of OT-specific types, but for all Java and JUnit launches (others will follow) the JRE-tab now contains a new subsection with a checkbox "Enable OTRE".

For projects with the OTJavaNature, this checkbox is enabled by default.

Old launch configuration types are still supported but we may want to fade out those. Should decide whether any migration aid is necessary here.

Re comment 1: the Team Activation tab only applies to Java applications (OT/Equinox defines this by the aspectBinding extensions). But yes, we should add the Team Activation tab to launches like JUnit, too. Should the "Enable OTRE" checkbox then migrate to the Team Activation tab? OTOH, also Equinox-launches have a JRE section and that's where I would add "Enable OTRE" for those launches, consistently grouping JRE and OTRE.

[stephan]

r18856 addresses the Team Activation tab, which now is uniformly added to the dialog for Java/JUnit launches iff the current project has the OTJavaNature.

Note: This patch requires a compiler as of r18849 (plus r18850, r18854).

[stephan]

Second part (regarding pde-launches with/without OT/Equinox) is implemented as a single team (PDEUILaunchingAdaptor) in r18887. The "Object Teams Runtime" block always appears next to the JRE block in the launch configuration dialog. For Eclipse Applications this is the main tab, for OSGi launches the "OSGi settings" tab.

Note that half the classes in org.objectteams.pde.ui are now legacy and can be removed once we can migrate old launch configurations to the new scheme.

[stephan]

r18907 extends the implementation of this issue to apply to JUnit-Plugin launches, too.

Note, that these launches inherit from standalone JUnit (=Java Application) launches, rather than from PDE launches, which required a few adjustments:

• different signature of getVMArguments (String vs. String[])
• possible interference with (undesired) launching via JMangler