Project code is hosted on http://git.eclipse.org/c
The project includes the necessary code to integrate any language server in the Eclipse IDE, interacting with the language server: it orchestrates the request to the language servers and presents the response in the usual IDE metaphors so users can manipulate them.
The default integration is to provide features into the Platform's Generic and Extensible editor, but some code may be used as API to let integration be done with other Eclipse-based editors.
Some examples of integration are:
Eclipse sim@openPASS provides a software platform that enables the simulation of traffic situations to predict the real-world effectiveness of advanced driver assistance systems or automated driving functions.
The Eclipse USS SDK provides a Java implementation of the USS REST API to allow for easy use of the Eclipse User Storage Service (USS) by Eclipse Foundation projects. The USS SDK handles the authentication and login capabilities required to use the USS from an Eclipse installation.
Capra provides traceability features. In essence, it allows the creation of trace links between arbitrary artefacts, as long as an adapter for these artefacts is available. This way, a trace link can be created between EMF model elements, source code files supported by the Eclipse Platform (e.g., Java, C, Python), or tasks from an issue tracking system supported by Eclipse Mylyn. External artefacts for which the Eclipse Platform does not offer built-in support can also be linked if a fitting adapter is provided.
StatET is an Eclipse-based IDE for R.
Eclipse TEA is a tasking orchestration engine that can be run from within the Eclipse IDE or headlessly. It is immediately concerned with tasks related to building and managing plug-ins for the Eclipse Platform, but is general enough to support other types of tasks and builds.
The Launch Configuration Generator is a small extension to the Eclipse IDE that allows to define launch configurations in a different way. Let me first elaborate on why the existing mechanism is sometimes not sufficient (on the other hand it is well suited for a lot of use cases, so we don't want to replace it completely!)
Groups can be composed of an arbitrary number of other launch configurations (launch groups can be members of other launch groups).
Additionally, conditions for members of the group can be configured to control when the group considers the individual launch to be “launched”.
The Open Standard Business Platform (OSBP) comprises a model-based software factory composed of extensible frameworks, tools and runtime environments for building, deploying and managing business applications across their lifecycles.