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"
(→Process guidelines) |
|||
| Line 63: | Line 63: | ||
=== Process guidelines === | === Process guidelines === | ||
* [https://www.eclipse.org/projects/efsp/ Eclipse Foundation Specification Process] | * [https://www.eclipse.org/projects/efsp/ Eclipse Foundation Specification Process] | ||
| + | * [https://jakarta.ee/about/jesp/ Jakarta EE Specification Process] | ||
</div> | </div> | ||
<div class="col-md-6"> | <div class="col-md-6"> | ||
| + | |||
=== Documentation === | === Documentation === | ||
* How-tos | * How-tos | ||
Revision as of 13:21, 29 April 2019
PLEASE NOTE: this page is Work In Progress and is expected to evolve in the upcoming weeks and months. We are welcoming input and suggestions as well as updates.
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.
Links
- home page
- project home page
- GitHub link
- Jenkins (CI)
- Roadmap ??
- Maven Repository ??
- Eclipse Practices on Git Usage
Jakarta EE Working Group
Specification project
Eclipse EE4J is a GitHub top-level project for Jakarta EE technology
Compatible Implementations
Adoptions
Communication
Google Calendar
Process guidelines
Documentation
- How-tos
- FAQ
- Articles
- Presentations
- White Papers
- Jakarta EE Community Google Drive
- Jakarta EE on YouTube
Eclipse Guides
- Common Build Infrastructure (Jenkins, Maven, etc.)
- Maven Nexus Repository
- Zoom conference tool guidelines