Community
Participate
Working Groups
An execution environment describes the capabilities of a Java runtime environment. For example, an excution environment may represent J2SE-1.4. The Java launching infrastructure supports an extensible set of execution environments to be contributed to the platform and for delegates to identify installed JREs compatible with an environment. This allows teams to build, run, and debug based on execution environments rather than being bound to specific installed JREs. Additionally, new APIs will allow JREs to be queried for system properties and specific JRE configurations will be able to be contributed to the set of installed JREs via an extension point. [JDT Core, JDT Debug]
3.2 RC1 Unfortunately, the support for execution environments has been added but is only exposed to Plug-in developers. Why has the decision been made to define execution environments only at PDE level? I don't see anything PDE specific in an J2SE-1.4 execution environment. I don't want to jump on on inter-op issue raised at http://www.xlml.com/aehso/2006/03/14/jcp-rubberstamping-and-eclipseorg-project-disarray/ but this hits exactly the point. :(
(In reply to comment #1) > Unfortunately, the support for execution environments has been added but is > only exposed to Plug-in developers. Filled as bug 137393.
This item actually belongs to JDT/Debug
marking fixed... execution environments have been in 3.2 since M4.
Please open other bugs as required.