The OSGi Technology Project will host open source OSGi technology projects which are adjacent to the OSGi Specification Project but don't produce OSGi specifications or TCKs for OSGi specifications. Such projects include testing support (JUnit 4, JUnit 5, AssertJ) for testing in OSGi runtimes, SLF4J bindings to the OSGi Log Service, and the enRoute OSGi development tutorials and examples. Additional projects can be added as proposed by the community.
The OSGi Specification Project is an open source initiative to create new, and evolve existing, software specifications, implementations of those specifications, and Technology Compatibility Kits (TCKs) for those specifications that enable development, deployment, and management of embedded, server-side and cloud-native applications.
The domain-specific language of Eclipse CommaSuite allows the specification of the provided and required interfaces of a software component. Each interface is described by means of (1) a signature, i.e., the set of commands, signals and notifications that are offered by a server, (2) a protocol state machine which describes the allowed sequences of interaction events between clients and server, (3) timing constraints on the occurrence of the events, and (4) data constraints on the values communicated.
The Eclipse LSAT project provides a toolkit for the early design of (mechatronics-intense) flexible manufacturing system development adhering to the MBSE paradigm. It enables the specification of the system and product flow in the system and analysis of the associated impact on system resources. The tool suite supports the early design of flexible manufacturing system development, by shortening the development time using light-weight models for logistics at an appropriate abstraction level.
AQAvit is the quality and runtime branding evaluation project for Java SE runtimes and associated technology. During a release it takes a functionally complete Java runtime and ensures that all the additional qualities are present that make it suitable for production use. These quality criteria include good performance, exceptional security, resilience and endurance, and the ability to pass a wide variety of application test suites. In addition to verifying that functionally complete runtimes are release ready, the AQA tests may also serve to verify new functiona
The Temurin Compliance project is responsible for obtaining, managing, and executing the Oracle Java SE Compatibility Kit (JCK) on Eclipse Temurin binaries. The work is done on private infrastructure and using code managed in closed repositories only available to committers of the Temurin Compliance. The public artefacts produced by this project are limited to an indication of whether a particular Eclipse Temurin binary is Java SE compliant or not.
The Temurin project provides code and processes that support the building of runtime binaries and associated technologies that are high performance, enterprise-caliber, cross-platform, open-source licensed, and Java SE TCK-tested for general use across the Java ecosystem.
"Eclipse OpenMCx" is an open, tool-neutral co-simulation middleware based upon Modelica  simulation standards, such as Functional Mock-up Interface (FMI)  and Distributed-Co-Simulation-Protocol (DCP) , aiming to support advanced simulation applications with a heterogenous toolchain in a distributed collaborative development process.
A language server implementation based on the Language Server Protocol for the Jakarta EE programming model. This LSP4Jakarta (Language Server for Jakarta EE) will provide core language support capabilities (such as code complete, diagnostics, quick fixes) to enable developers to easily and quickly develop cloud-native applications using the Jakarta EE APIs.
The Eclipse client for the Language Server for Jakarta EE will surface the capabilities provided by the language server to developers using the Eclipse (desktop) IDE.
Machine learning (ML)-based functions – especially methods that continue the learning process online – cannot be approved by current methods and standards (e.g. ISO 26262). One approach to address this issue is to introduce an online verification module, that constantly checks and guarantees the function of interest to stay within safe bounds. That way, safety guarantees can be provided for an ML-based function.