Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Jakarta EE"
(→Specification project teams) |
|||
| Line 31: | Line 31: | ||
<td valign="top"> | <td valign="top"> | ||
| − | == Specification project | + | == Specification project == |
</td> | </td> | ||
| + | * [https://github.com/eclipse-ee4j GitHub link to top level Eclipse EE4J project] | ||
| + | * [https://github.com/eclipse-ee4j/jakartaee-platform GitHub link to Jakarta EE Platform project ] | ||
<td valign="top"> | <td valign="top"> | ||
Revision as of 12:34, 22 April 2019
The Future of Cloud Native Java In order to accelerate business application development for a cloud-native world, leading software vendors collaborated to move Java EE technologies to the Eclipse Foundation where they will evolve under the Jakarta EE brand.
Eclipse EE4J is a GitHub top-level project for Jakarta EE technology [1]
Links
|
Jakarta EE Working Group |
Specification project |
Compatible ImplementationsAdoptions |
|||
CommunicationGoogle Calendar |
Process guidelines |
Documentation
|
|
Eclipse Guides
|
Eclipse Mailing Lists |
|