Eclipse EE4J

The initial scope of the EE4J project during late CY2017 and early CY2018 is to transition existing Java EE 8 technologies to the project and to define processes for evolving the platform:

A core set of Java EE 8 technologies, including GlassFish technologies, and Java EE technologies for which Oracle is the specification lead, forms the initial core of the EE4J platform.
This core includes sources for Java EE 8 Reference Implementations (RIs), Technology Compatibility Kits, project build and test scripts, and product documentation sufficient to build a documented RI from Eclipse Enterprise for Java sources and other software available in open source.
Some of the EE4J API implementations and technology compatibility kits continue to be available in other open source projects.
The initial Eclipse Enterprise for Java RI is compatible with GlassFish 5.0, and passes Java EE 8 compatibility tests transitioned to EE4J.

EE4J defines a process for evolving the platform, including updating existing APIs, implementations, and technology compatibility kits, as well as creating new APIs, implementations, and technology compatibility kits. The goal of platform evolution is to enable ongoing delivery, over time, of compatible Java runtime implementations that meet the needs of developers and administrators of server-side and cloud-native applications. In addition to providing an integrated platform, many EE4J projects and technologies can be run standalone in Java SE environments.

EE4J is open to incorporation, integration, and support for innovations that enhance the development, deployment, and management of server-side and cloud-native applications. These include innovations introduced in other open source projects, including closely related projects. Eclipse MicroProfile is such a project that EE4J will review as a source of innovations for incorporation into EE4J.

The projects under this top-level project will be implemented in Java. These projects support many different hardware, OS, and database environments to meet the needs of developers, administrators, application end users, vendors, and partners.

Basics

Project ID: ee4j
PMI: https://projects.eclipse.org/projects/ee4j
Website: https://projects.eclipse.org/projects/ee4j
Download CSV: Commits , Issues , Reviews , IP Lab requests
Time range for commits: 2025-01-24 18:59:34 to 2025-05-27 07:37:09.
Time range for issues: 2025-01-13 08:00:20 to 2025-09-09 19:13:38.
Time range for reviews: 2025-01-24 19:00:18 to 2025-06-13 06:24:16.

Repositories

Repo	Commits	Reviews	Issues
https://github.com/eclipse-ee4j/ee4j	8	4	4
https://github.com/eclipse-ee4j/.github	0	0	1

Activity - commits

There have been 8 commits made by 3 people on 1 repositories over the last 12 months.

Activity - issues

There have been 5 issues submitted by 5 people on 2 repositories over the last 12 months.

Activity - reviews

There have been 4 reviews submitted by 3 people on 1 repositories over the last 12 months.

The EMO oversees the lifecycle of Eclipse projects, trademark and IP management, and provides a governance framework and recommendations on open source best practices.

See the project’s PMI page at https://projects.eclipse.org/projects/ee4j

Releases

IP Lab requests

Organization Settings

GitHub organization: eclipse-ee4j
2FA enforced: True
Default workflow permissions: write

Branch Protections

This project has a total of 101 repositories in its associated GitHub organization eclipse-ee4j . The graph below outlines the percentange of repositories that have either defined a Branch Protection Rule or Repository Ruleset: