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

Linux 5.4 Lands A Number Of Memory Management Fixes

While mid-way through the Linux 5.4 development cycle with RC4 due out on Sunday, a number of memory management fixes just hit the mainline kernel. Andrew Morton's pull request was merged on Friday night and he noted, "Rather a lot of fixes, almost all affecting mm/" Indeed there were memory management fixes in this pull ahead of 5.4-rc4. Changes include a zRAM race condition fix, avoiding access to uninitialized memory maps, allow dropping transparent huge-pages (THP) from the page cache, and other fixes in this area including the possibility of a kernel crash. Read more Also: Intel's Cloud Hypervisor 0.3 Adds Block Device Offloading, Paravirtualized IOMMU

Programming: eMMC Flash, Compilers and Python

  • Some Tesla EV’s Control Screens Went Dark as Excessive Logging killed the eMMC Flash

    Despite wear-leveling techniques, eMMC flash memories tend to wear out over time as they have limited write cycles.

  • AMD Zen 2 Improvements For LLVM Have Been Held Up For Months By Code Review

    Back in February for LLVM Clang 9.0 was the initial AMD Zen 2 "znver2" enablement, but like the GCC support at the time it was the very basics. With time GCC picked up Zen 2 scheduler improvements and other work while sadly in the case of LLVM the improvements are still pending. Back in August, AMD's Ganesh Gopalasubramanian sent out the znver2 scheduler model for LLVM for Zen 2 CPUs but a focus on the EPYC 7002 "Rome" processors. "There are few improvements with respect to execution units, latencies and throughput when compared with znver1. The tests that were present for znver1 for llvm-mca tool were replicated. The latencies, execution units, timeline and throughput information are updated for znver2."

  • Python Add Lists

    This tutorial covers the following topic – Python Add lists. It describes various ways to join/concatenate/add lists in Python. For example – simply appending elements of one list to the tail of the other in a for loop, or using +/* operators, list comprehension, extend(), and itertools.chain() methods. Most of these techniques use built-in constructs in Python. However, the one, itertools.chain() is a method defined in the itertools module. You must also see which of these ways is more suitable in your scenario. After going through this post, you can evaluate their performance in case of large lists.

  • StackOverflow Report: (cxcix) stackoverflow python report

today's howtos

  • How to install Chromium on Ubuntu using SNAP
  • 3D using Godot

    It is time for another installment of Godot (previous entries: introduction, 2D). This time, I have dived into the world of 3D. The goal is to recreate parts of an old time favorite: Kosmonaut. Something I remember playing a lot on my dad’s 286 with amazing EGA graphics. The state of the game when writing can be seen in the short screen capture below. This is more of a tech demo status than a full game at the moment, but I hope you will still find it interesting. You can also get the complete source code. [...] Once we have a world with a track (the grid map), we add a player to the scene (the yellow blob in the image above – I need to learn Blender to create a proper ship). The player scene contains the ship – and the camera. This means that the camera follows the player automatically – very convenient. The player script is responsible for this ship’s movements based on user input. Inputs can either be pressed for a long time, used for sideways movement, or just tapped (i.e. the release is ignored), used for jumping. Each of the inputs are mapped to a keyboard key (or other input device) in the Project Settings dialog, under the Input Map tab. This feels a bit awkward to me and makes me lose the feeling of flow – but I don’t know how to do it better.

  • How to install OpenOffice on Linux
  • How To Install Free SSL Certificate for Apache on CentOS 8
  • Install VirtualBox 6 on CentOS 8
  • How to Install Odoo 13 on Ubuntu 18.04
  • How to Install Anaconda on Debian 10
  • Install Shutter Screenshot Tool via PPA in Ubuntu 19.10

Xfce 4.16 development phase starting

In the 4.14 cycle we tried to do a 1:1 port of what used to be our Gtk2 desktop environment, avoiding visual changes. In the 4.16 cycle we plan to harmonize the appearance of certain elements that either became inconsistent through the port or already were inconsistent before (e.g. toolbars or inline toolbars). We will also play with client-side decorations where we feel it makes sense (for instance replacing the so-called XfceTitledDialog, that is used for all settings dialogs with a HeaderBar version). Before anyone gets too excited (both positively or negatively): It is not planned to redesign more complex applications (like Thunar) with Headerbars in 4.16. We will however try to keep the experience and looks consistent, which means gradually moving to client side decorations also with our applications (please note that client side decorations are not the same as HeaderBars!). Through this change e.g. “dark modes” in applications will look good (see the part about the Panel below). Now before there is a shitstorm about this change I would kindly ask everyone to give us time to figure out what exactly we want to change in this cycle. Also, switching to client-side decorations alone is not a big visual departure – feel free to also dig through the client-side decorations page if you want to read/see more on this. Read more