Eclipse Collections is a collections framework for Java. It has JDK-compatible List, Set and Map implementations with a rich API, additional types not found in the JDK like Bags, Multimaps and set of utility classes that work with any JDK compatible Collections, Arrays, Maps or Strings. The iteration protocol was inspired by the Smalltalk collection framework.
Apache Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information.
MDHT delivers a standard object-oriented alternative to proprietary development methodologies and tooling used to specify and implement most healthcare industry standards. There are three primary categories of users for MDHT tools: authors of healthcare industry interoperability standards, certification or testing authorities who validate that an Electronic Health Record (EHR) system produces XML or JSON files that comply with the standard, and software developers that implement adapters or applications that produce and consume healthcare data.
The purpose of this project is to provide a set of Eclipse plug-ins that provide code review capabilities in the Eclipse IDE.
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.
EASE allows the execution of script code (using scripting languages such as JS, Python, ...) within the context of the Eclipse Platform/RCP. As they are running in the same JRE as Eclipse itself, these scripts have direct access to any class of your application and may interact with your workbench.
Lua Development Tools (LDT) is about providing Lua developers with an IDE providing the user experience developers expect from any other tool dedicated to a static programming language.
Like many other dynamic languages, Lua is so flexible that it is hard to analyze enough to provide relevant and powerful tooling.
LDT is using Metalua, to analyze Lua source code and provide nice user assistance.
RCP Testing Tool allows create and execute test cases for Eclipse-based applications with minimal effort. The minimal required configuration of applications under test is as simple as browsing for a folder for binary AUTs or choosing a PDE launch configuration for AUTs from sources. A typical workflow to create a test case which should work in most cases looks like this: capture an application state, record test actions, add assertions. More complex activities including test parameterization, extracting common pieces of functionality into reusable actions, writing test cases manually before UI, and test case debugging are also available. Developers can extend the tool's functionality to add record/replay support of custom widgets and capture/apply support of custom aspects of an application state.
For more details on RCPTT visit http://eclipse.org/rcptt.
Eclipse Californium (Cf) is an open source implementation of the Constrained Application Protocol (CoAP). It is written in Java and targets unconstrained environments such as back-end service infrastructures (e.g., proxies, resource directories, or cloud services) and less constrained environments such as embedded devices running Linux (e.g., smart home/factory controllers or cellular gateways).
Handly provides basic building blocks for handle-based models, with an emphasis on language-specific source code models of Eclipse workspace. It allows creating highly scalable, robust, and thoroughly optimized models similar in design principles to the tried-and-tested Java model of Eclipse Java developement tools while reducing programming effort, fostering software reuse, and enabling interoperability.
Handly is designed for flexibility and can be used for implementing a handle-based source code model for practically any language, whether general-purpose or domain-specific; it is compatible with any parsing technology. Since version 0.5 (to be released soon), the model implementor has complete control over the model's base-level API, including the ability to implement a preexisting handle-based model API. At the same time, the provided uniform meta-level API establishes a common language and makes it possible for IDE components to work in a generic way with any Handly-based model.