The datasets provided by this project can already be explored at https://download.eclipse.org/scava/ .
The intent of the proposed Eclipse Adoptium Incubator is to foster collaboration, and hopefully results in work proceeding to contribution by their original authors into upstream projects, including OpenJDK, or moving the work into a new Eclipse Adoptium project. The Adoptium Incubator would not make any releases itself.
The companies involved want to increase the automotive industry’s competitiveness, improve efficiency through industry-specific cooperation and accelerate company processes through standardization and access to information and data. A special focus is also on SMEs, whose active participation is of central importance for the network’s success. That is why Catena-X has been conceived from the outset as an open network with solutions ready for SMEs, where these companies will be able to participate quickly and with little IT infrastructure investment.
Eclipse Exousia implements Jakarta Authorization, a technology that defines a low-level SPI for authorization modules, which are repositories of permissions facilitating subject based security by determining whether a given subject has a given permission, and algorithms to transform security constraints for specific containers (such as Jakarta- Servlet or Enterprise Beans) into these permissions.
Eclipse Exousia provides default implementations of these authorization modules and algorithms, as defined and mandated by the Jakarta Authorization specification.
The Public Access Submission System (PASS) is a platform to assist researchers in complying with the access policies of their funders and institutions.
Eclipse s0nar carries out the automatic versioning of datasets, the Data Science work of data analysis, cleaning and selection and the machine learning work of model adjustment and training. All these phases are configurable, being able to adjust the requests to the specific use case to be solved.
There are many reasons why a system’s behavior over time is difficult to understand or, worse, confusing – even when the system is performing as designed. An example is a situation in which many concurrent activities share resources. Unforeseen interactions may arise due to the specific timing of the activities. Moreover, if the timing of the activities changes (e.g. due to an upgrade to the computational platform), the interactions may also change, which could result in significantly different behavior.
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.