The LJC Joins Jakarta EE (Java EE evolved!)

What’s Jakarta EE?

Over on Jakarta EE you’ll see our new LJC logo as a Participant member.  This blog post details what Jakarta EE is and what the LJC hopes to achieve within its community!

Jakarta EE is the new brand name for Java EE. For those who missed it, the Java EE platform was recently donated to the Eclipse Foundation (as Eclipse EE4J), the FAQ gives the background to this.

The existing Java EE 8 platform is being migrated to the Eclipse Foundation.  There’s a lot of new build farm activity taking place and the end goals for 2018 are:

  • Q3 2018 – Release Java EE 8.0 by the Eclipse Foundation.
  • Q4 2018 – Release Jakarta EE 8.0 projects (which will be identical code wise to Java EE 8.0) by the Eclipse Foundation.

Both of these releases will be certified against the appropriate TCKs (which are also being open sourced and donated to Eclipse).

In parallel the community at large is looking to the future of Java for enterprise developers.  A future which is lightweight, fast, cloud native and micro services based.  This work has already started and vibrant discussions (for example, around the role of the Servlet container and what types of profiles make sense in a modern world) are taking place on several mailing lists. We highly recommend you sign up to the lists and join in!

LJC’s role in Jakarta EE

The LJC currently holds technical, legal/oversight and advocacy roles at the Java Community Process (JCP) which is the existing standards body for Java EE today.  We hope to continue serving the interests of the day to day Java developer in those capacities at Jakarta EE and have nominated ourselves for the corresponding working groups (Steering, Specification and Marketing).

Next Steps

Are you a day to day Java developer then please come and join us on mailing lists and have your voice heard.  If you’re unsure on what’s going on or are nervous about speaking up, then contact us at the LJC and we’ll be happy to help.

Cheers,

Martijn (on behalf of the LJC Standards Committee)