The purpose of this project is to provide a set of Eclipse plug-ins that provide code review capabilities in the Eclipse IDE.
The Ignite|IoT methodology has two main perspectives:
Dirigible is an open source project that provides Integrated Development Environment as a Service (IDEaaS) as well as runtime containers integration for the running applications. The environment itself runs directly in browser and therefore does not require additional downloads and installations. It packs all the needed components, which makes it self-contained and well integrated software bundle that can be deployed on any Java based Web Server.
RISE V2G allows you to create an EVCC instance acting as the client sending request messages related to the respective charging scenario as well as an SECC instance acting as the server which is responding to those requests. EVCC stands for Electric Vehicle Communication Controller (inside the EV) whereas SECC is short for Supply Equipment Communication Controller (inside the EVSE).
Leshan is an OMA Lightweight M2M (LWM2M) implementation in Java.
The Vorto project comprises of the meta information model, the tool set to create information models, the code generators and the repository to manage existing information models. The meta information model and also the tool set are based on the Eclipse EMF (Eclipse Modeling Framework) framework.
The purpose of Andmore is to provide Android Eclipse tooling without having to go through multiple steps.
The technology development will involve integrating and refactoring the Google ADT plugins as necessary to work with the project. Similarly, the former MOTODEV plugins have many useful components that can be integrated into the project. Once these are integrated, new components may be added.
Titan provides an Eclipse-based IDE for TTCN-3. The user of the tool can develop test cases, test execution logic and build the executable test suite for one or more platforms.
The project aims to develop and sustain the necessary tooling that will assist Cloud application lifecycle management operations, using open standards and languages, where appropriate. As aforementioned, these operations are classified into three distinct categories: (1) application description, (2) application deployment and (3) application monitoring. CAMF will follow the Eclipse OSGi plug-in based software architecture for each of the aforementioned operations and will inherit the same look-and-feel that Eclipse users are accustomed to.