Language Selection

English French German Italian Portuguese Spanish

Java finally goes all in on open source with the Jakarta EE 8 release

Filed under
OSS

Java being fully open-sourced has been a long, long time coming. While Sun open-sourced some of Java as long ago as November 2006, actually using Java in an open-source way was… troublesome. Just ask Google about Android and Java. But for Java in the enterprise things have changed.

On September 10, The Eclipse Foundation announced the full open-source release of the Jakarta EE 8 Full Platform and Web Profile specifications and related Technology Compatibility Kits (TCKs).

This comes after Oracle let go of most of Java Enterprise Edition's (JEE) intellectual property. Oracle retains Java's trademarks though -- thus Java EE naming convention has been changed to Jakarta EE. But for practical programming and production purposes Jakarta EE 8 is the next generation of enterprise Java.

Read more

The Eclipse Foundation Releases Jakarta EE 8 Specifications

  • The Eclipse Foundation Releases Jakarta EE 8 Specifications; Completes Transition to Eclipse Foundation as the New Home for Open Source Cloud Native Java

    The Eclipse Foundation today announced during the JakartaOne Livestream virtual conference the release of the Jakarta EE 8 Full Platform and Web Profile specifications and related Technology Compatibility Kits (TCKs). This release provides a new baseline for the evolution and innovation of enterprise Java technologies under an open, vendor-neutral, community-driven process. As a result, Java vendors, developers, and customers alike now have a foundation for migrating mission-critical Java EE applications and workloads to a standard enterprise Java stack for a cloud native world. This release represents a major milestone for the world’s leading innovators in cloud native Java, including Fujitsu, IBM, Oracle, Payara, Red Hat, Tomitribe, and dedicated independent community members who are collaborating at the Eclipse Foundation to advance Jakarta EE, the successor to Java EE.

Authored by Sean Michael Kerner

Jakarta EE 8: The new era of Java EE explained

  • Jakarta EE 8: The new era of Java EE explained

    Java EE is a fantastic project. However, it was created in 1999, under the name of J2EE, and is 20 years old, which means it also faces challenges in keeping pace with enterprise demands.

    Now, Java EE has a new home and a new brand. The project was migrated from Oracle to the Eclipse Foundation, and it is called Jakarta EE, under the Eclipse Enterprise for Java (EE4J) project. The Eclipse Foundation released Jakarta EE 8 on September 10, and in this article, we’ll look at what that means for enterprise Java.

    Java EE was a very strong project that was widely used in many kinds of enterprise Java applications and many big frameworks, such as Spring and Struts. Developers may have questioned its features and evolving processes, but looking at its high usage and time in the market, its success is undeniable. Nonetheless, the enterprise world doesn’t stop, and new challenges emerge all the time. The speed of change has increased, with new technologies such as cloud computing being developed to provide better solutions, and Java EE needed to keep pace as well.

Hey, We're Open Source Again! Eclipse Unveils Jakarta EE 8

  • Hey, We're Open Source Again! Eclipse Unveils Jakarta EE 8

    The enterprise developers’ edition of Java has gone completely open source with a new version managed entirely by the Eclipse Foundation. The Foundation released Jakarta EE 8 with a flourish yesterday.

    Jakarta took a winding road to get to this point. Originally called J2EE when released in 1999, it was renamed to Java EE in 2006. Then, Oracle bought Sun three years later, which locked the product up in Fort Larry for the best part of a decade.

    Citing a wish to make things more open, it agreed to give Java EE back to the open source community in 2017, choosing the Eclipse Foundation. While it gave the Foundation the IP rights to the code, though, it held onto the name. So Eclipse had to find another one. Hence, Jakarta.

Jakarta EE now operates under open, community-driven process

  • Jakarta EE now operates under open, community-driven process

    After transitioning from Oracle to the Eclipse Foundation in 2017, Jakarta EE (previously known as Java EE), has reached another major milestone.

    With today’s release of the Jakarta EE 8 Full Platform and Web Profile specification, the project now has a new baseline for having an “open, vendor-neutral, community-driven process.” Now, Java vendors, developers, and consumers will have a foundation for migrating Java EE applications to a standard enterprise Java Stack.

More and the original

The Eclipse Foundation Wins Duke’s Choice Award

  • The Eclipse Foundation Wins Duke’s Choice Award for Open Source Contributions to the Java Ecosystem

    The Eclipse Foundation was awarded a Duke’s Choice Award yesterday in recognition for outstanding open source contributions to the Java ecosystem and the community-driven achievement of moving Java EE technologies from Oracle to the Jakarta EE Working Group. Held at the Oracle Code One conference and tradeshow, the Duke’s Choice Awards celebrate invaluable innovation in Java-based technologies and contributions to Java.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

today's howtos

Gateworks Venice Industrial IoT SBC Family Features Dual Ethernet and mPCIe Sockets

The company provides a Linux Ubuntu Board Support Package for the board, as well as a GW7300 Development Kit (GW11049) with the board, U-Boot bootloader, the Linux BSP, interface cables as appropriate for the SBC, a power supply, and a JTAG programmer to update firmware and provide serial console access. Read more

Android Leftovers

today's leftovers

  • Soldat 2 brings the next-generation of fast-paced online platformer action - out now

    Available now in Early Access, the online platformer shooter Soldat 2 brings in the full charm of the original classic that took the early internet by storm and will continue to expand it. If you played the original - right now it's very much as you expect. Fast paced, ridiculous, seriously easy to get into and really rather fun. You can't ask for much more in a military-style platformer shooter, it does exactly what it sets out to do. You run, you throw a grenade, you spray and pray and hopefully get a few frags along the way. Slightly prettier than the original but still just as insane. [...] Plenty more is to come including more of pretty much everything: levels, weapons, vehicles - you name it and it probably will get it at some point. The big idea with Soldat 2 is to be a platform for others to create, as much as it is a game itself so it's going to have full modding support for all sorts of community content.

  • VirtualBox, 15 practical examples
  • Fedora 32 : Testing the Bookworm software.
  • AMD Dimgrey Cavefish and VanGogh Support Lands In Radeon Linux OpenGL Driver

    The latest enablement work landing in the RadeonSI Gallium3D open-source driver is for AMD Dimgrey Cavefish and VanGogh. Merged today to Mesa 20.3-devel was VanGogh and Dimgrey Cavefish support. VanGogh and Dimgrey Cavefish are both GFX10.3 (Navi 2) parts. Van Gogh has been rumored for a while as a next-gen mobile API with Zen 2 CPU cores and RDNA2 graphics in the 7.5~18 Watt TDP space. Details on Dimgrey Cavefish are light as it's another Linux-specific codename for a Navi 2 part in following the X.Org color + fish family naming convention.

  • Updates for CAP Deployment in public clouds

    Our vision for the SUSE Cloud Application Platform Deployment tool is to provide the simplest experience possible and do so across a variety of supported cloud service providers. Since my last post we’ve made some significant strides, so it’s time to catch up on our status.

  • Create and import COCO datasets into Maximo Visual Inspection

    A lot of work has gone into the labeling UI for IBM Maximo Visual Inspection (MVI). However, there are situations where you want to work with an already existing dataset that was created outside of MVI. Thankfully, MVI already supports importing COCO datasets, label information and all. That’s easy enough. But what if you want to modify or add some images before importing that dataset? Maybe you have some colleagues without access to MVI who need you to keep things in a common format? Or maybe there are other tools that interact with these datasets? We can’t expect everyone else to use MVI’s dataset format. I’m hoping this post will help you along in figuring how to do what you need to do outside of MVI. We’re going to create our own little COCO dataset with LabelMe and LabelMe2coco, and turn that into an MVI dataset that we can train MVI models with.

  • Linux on Lenovo, jdk transition to Git, and more industry trends

    The impact: That is an epic list of achievements on behalf of all of us that use Linux on the desktop. Kudos and thank you to the Fedora Desktop team!

  • Red Hat OpenShift Container Storage 4.5 Delivers Kubernetes-Based Data Services