Life at Eclipse

Musings on the Eclipse Foundation, the community and the ecosystem

Posts Tagged ‘Java

The Eclipse IDE Working Group Celebrates Its First Anniversary

Today we celebrate the one year anniversary of the Eclipse IDE Working Group. A year ago, the Eclipse Foundation launched this Working Group focused on the Eclipse IDE and the Eclipse Simultaneous Release (SimRel). We would like to share some of our successes since the launch of the Working Group in April 2021. 

Highlights

  • 20 Years of the Eclipse IDE: 2021 was a momentous year for the Eclipse IDE, as we celebrated its 20 year anniversary!
  • Welcome Ed! Ed Merks joined us as a SimRel Architect and Release Engineer. Ed’s first set of tasks included preparing PGP signing support for the 2022-06 release and mapping out the project dependencies.
  • Productive collaboration Our collaboration with the Planning Council has been very effective. We have identified the top issues as outlined by the Planning Council and have a plan to address them.

PGP: A Community Success Story

A great community success story for the Eclipse IDE Working Group is the delivery of a fully-functional, secure PGP implementation for Eclipse 4.23 (SimRel 2022-03). This enhancement augments Eclipse’s existing security support which is based on jar signing. Jar signing has the significant drawback that artifacts originating from external dependencies must be modified in order to sign them, i.e., jar signatures are intrinsic to the artifact. In contrast, PGP signatures are extrinsic to the artifact and have long been used in Maven repositories to provide certification of origin. Eclipse’s PGP support facilitates significantly streamlined consumption of Maven-based artifacts by Eclipse projects, making it easier for our community to exploit and deliver the latest and greatest libraries with each quarterly simultaneous release.

The initial proof-of-concept PGP implementation was contributed by Mickael Istria. In combination with Mickael’s on-going participation, along with Christoph Läubrich’s technical insights, the working group has helped to harden the PGP implementation to industrial-strength quality for the SimRel 2022-03 delivery. Even the existing support for jar signing has been improved, as users can now easily save trusted X.509 certificates to avoid repeated trust prompts as is typical with self-signed certificates. Issue 11 provides a detailed track record of all the activities around PGP signing during the 2022-03 release cycle as well as additional background information.

With this groundwork in place, our community as a whole can exploit PGP signing for broader adoption in the Eclipse 4.24 (SimRel 2022-06) delivery this coming June.

Planning Council’s Top 3 Items

The Planning Council plays an important role in the Eclipse IDE WG. The Planning Council can be seen as the “technical” arm of the WG. At the beginning of the first year, under the leadership of Mélanie Bats, the Planning Council was tasked by the Steering Committee to identify the top issues affecting the successful release and adoption of the Eclipse IDE as a platform and a product.

After much brainstorming and debate the Planning Council recommended the “top three” items to the Steering Committee to focus on:

  • The “Bus Factor“, particularly of the release engineering processes of the Simultaneous Release (SimRel).
  • Identifying individual project risks, for example identifying which projects contributing to the SimRel are under-resourced and understanding which downstream projects are affected.
  • Updating the graphical layer Eclipse where it is lagging behind operating system changes, for example improving dark mode, better operating system and web browser integration.

The Steering Committee took these items and translated them to action points that are now being carried out and has allocated a substantial portion of the IDE WG’s budget to improving these common parts of the Eclipse IDE. The highlights of this work include:

  • Hiring Ed Merks as the SimRel release engineer.
  • Ed has also found time to start mapping out the incredibly complicated dependency graphs between the dozens of different projects contributing to the SimRel to better understand the impact of any particular project discontinuing participation and to fully understand the dependency chain of each bundle in the SimRel repository.
  • The Eclipse Foundation has created new guidelines for funding work such as the graphical layer improvements. This is the most recent action point and already some bugs are being fixed under this program.

One year into the Eclipse IDE WG and Jonah Graham is now the chair of  the Planning Council. The Planning Council is pleased to see some concrete actions taking place under the new Working Group. The structures and processes in the Working Group have progressed well and additional funding of the IDE WG will see direct improvements in the quality, stability and adoption of the Eclipse IDE.

Engage in the Working Group

We still have much to do! If you are interested in joining us and supporting the development of the Eclipse IDE technology stack, improving the user experience of the platform, and making it more attractive for organisations, let us know. We welcome the opportunity to speak with everyone who wants to help shape the future of the Eclipse IDE.

The resources funded by the IDE Working Group members are really paying dividends for our community, both for the producers and for the consumers. If you’re a consumer, please consider investing in our community’s ongoing success by supporting the Eclipse IDE with funding, contributions, new ideas, new points of view, and by getting directly involved in development efforts. Better funding enables us to achieve more, and more hands make the work lighter.

If you are interested in becoming a Working Group member, you can get in touch with us by completing the membership form or by sending an email to the Membership Coordination Team. If you are interested in becoming a sponsor, let us know.

Stay In Touch

We love exchanging ideas, so if you have any questions or would like to know more about what we do here, connect with us!  You can also join our meetings to find out more about what we’re up to. They are open to the community and take place every 2 weeks from 2:30pm to 3:30pm (CET) on Tuesdays. Or you can contact a member of the steering committee, we’re always happy to talk to you.

Written by Mike Milinkovich

April 26, 2022 at 8:01 am

Posted in Foundation

Tagged with ,

Meet Adoptium: Open Source Java Runtimes for Enterprises

Today we announced the creation of the Adoptium Working Group, whose mission is to bring high-quality, open source Java runtimes to millions of developers building the next generation of enterprise applications.

Adoptium was created in collaboration with the AdoptOpenJDK Technical Steering Committee, and supports the Eclipse Adoptium top-level project. The working group provides the vendor-neutral governance, infrastructure, marketing, community building, and developer advocacy work needed to ensure timely releases of Java runtimes and strengthen the project’s community.

The Adoptium project continues the work initiated by the AdoptOpenJDK community. The project gives developers a trusted location where they can download fully compatible, high-quality distributions of Java runtimes based on OpenJDK source code. In a few short years AdoptOpenJDK became the leading provider of OpenJDK-based binaries used to power production workloads in embedded systems, desktops, traditional servers, modern cloud platforms, and mainframes. Adoptium will continue that mission as a vendor-neutral, multi-vendor initiative hosted at the Eclipse Foundation. We appreciate the trust that the AdoptOpenJDK TSC has placed in us as we become the new stewards of this amazing community.  

The founding members of the working group include numerous Java developers, as well as vendors such as Alibaba Cloud, Huawei, IBM, iJUG, Karakun AG, Microsoft, New Relic, and Red Hat. This strong participation clearly shows the value the industry sees in transitioning the widely adopted AdoptOpenJDK technologies and community to the Eclipse ecosystem. I would also like to recognize the efforts of Oracle in negotiating a TCK license agreement with us in support of this initiative.

Benefits for the Global Java Ecosystem

Developers and enterprises need a dependable source of open source, compatible Java runtimes that are fully supported with timely patches and updates. AdoptOpenJDK was created in 2017 to provide a community-based solution to this requirement, delivering open build and test systems for OpenJDK across multiple platforms, and delivering high quality binaries for use. Developers responded enthusiastically, downloading more than 240 million Java binaries from AdoptOpenJDK.

Moving the AdoptOpenJDK technologies and community to the Eclipse Foundation benefits the AdoptOpenJDK community and the many members of the global Java ecosystem:

  • The AdoptOpenJDK community can leverage our governance framework and intellectual property services, as well as our developer advocacy, marketing, legal, and hosting capabilities, to help ensure the AdoptOpenJDK initiative and community continue to flourish. The community can strengthen its vendor independence, while maintaining a strong relationship with existing sponsors and the Java community as a whole.
  • Developers and enterprises in the Java ecosystem have reliable access to fully compatible Java runtimes for hybrid cloud and multi-cloud enterprise development.

Adoptium complements the other Java-based projects already hosted at the Eclipse Foundation, including the Jakarta EE and MicroProfile specification communities, and open source projects such as Eclipse GlassFish, Eclipse Jetty, and Eclipse Vert.x.

I want to thank everyone who was involved in establishing the Adoptium Working Group. I also want to welcome everyone from the AdoptOpenJDK community to the Eclipse Foundation, and encourage you to continue building on the character and spirit of your great community.

Get Involved in Adoptium 

There are a few different ways to get involved in the Adoptium community at the Eclipse Foundation:

Written by Mike Milinkovich

March 23, 2021 at 8:00 am

Posted in Foundation, Open Source

Tagged with ,

Introducing the Jakarta EE Specification Process

I am very happy to announce that we are publishing a draft of the Eclipse Foundation Specification Process for community review and feedback. This specification process will be used by Jakarta EE as the new open specification process, replacing the JCP process previously used for Java EE. It is also expected that this new process will be of interest to other Eclipse working groups.

We are really looking forward to your feedback, which you can do via the Jakarta EE Community mailing list (preferred), or on the document comments.  The feedback provided will be used as input to finalizing a first version of the specification process and its adoption by Jakarta EE and other working groups at the Eclipse Foundation.  

As you are reviewing this draft specification process, please keep in mind the following key points about the approach that was taken by the Specification Committee.

  1. We want to design a specification process to replace the JCP. While there are many differences with the JCP, the key objective was to make the whole process as lightweight as possible.
  2. We want the specification process to be as close to open source development as possible. This is actually not a trivial exercise, as by its very nature drafting specifications is a somewhat different process.
  3. This is the Eclipse Spec Process, so we want to reuse the Eclipse Development Process wherever possible, and we want to ensure that the general flow and tone of the EDP is followed.
  4. We want to create a process that allows code-first development. Specifically, we want to enable a culture where experimentation can happen in open source and then have specifications be based on those experiences.
  5. We want the specifications that result from this process to be as high quality as possible. In particular, this means that we need to take care of the intellectual property flows, and to protect the community’s work from bad actors. This requirement manifests as two fundamentally important differences from the EDP:
    • Specification Committee approval is required for releases from Spec Projects, in addition to the normal PMC approval; and
    • We introduce the notion of “Participants” who are committers who represent specific member companies on a Spec Project. This is necessary to ensure that the IP contributions (particularly patents) from companies are properly captured by the process.

All of us at the Eclipse Foundation would like to recognize the tireless efforts of the members of the Specification Committee. A lot of hard work has gone into this document, and it’s very much appreciated. We are certain that Jakarta EE, and many other Eclipse technologies, benefit from the thoughtful efforts of this Committee.  In particular, we would like to thank the following Specification Committee members and alternates:

Fujitsu: Kenji Kazumura​, Mikel DeNicola
IBM: Dan Bandera​, Kevin Sutter
Oracle: Bill Shannon​, Ed Bratt​, Dmitry Kornilov
Payara: Steve Millidge​, Arjan Tijms
Red Hat: Scott Stark, Mark Little
Tomitribe: David Blevins​, Richard Monson-Haefel
PMC Representative: Ivar Grimstad
Elected Members: Alex Theedom, Werner Keil​

I also wish to recognize Tanja Obradovic and Wayne Beaton from the Eclipse Foundation team who have driven the process throughout – many thanks to you both!

Written by Mike Milinkovich

October 16, 2018 at 3:18 pm

Posted in Foundation, Jakarta EE, Open Source

Tagged with , ,

And the Name Is…

We are happy to announce that the new name for the technology formerly known as Java EE is….[insert drumroll]… Jakarta EE.

Almost 7,000 people voted in our community poll, and over 64% voted in favour of Jakarta EE. Thanks to everyone who voted, blogged, or tweeted! This has been quite the process, and we are all really happy with the community support throughout.

naming_poll_results

As we have been making progress on migrating Java EE to the Eclipse Foundation there have been a lot of moving pieces and parallel threads, especially around naming. Thankfully, we think we are getting to the end of this, and the names at least are starting to sort themselves out.  We have prepared this handy table to assist with the translation from the old names to the new names.

Eclipse Jakarta Working Group

Old Name New Name
Java EE Jakarta EE
Glassfish Eclipse Glassfish
Java Community Process (JCP) [*] Jakarta EE Working Group (Jakarta EE)
Oracle development management Eclipse Enterprise for Java (EE4J)
Project Management Committee (PMC)

Note that permission for products to formally use the Jakarta EE trademark will be dependent upon passing a as-yet-to-be-defined compatibility program run by EE.next. However, as of today, it is preferred that when you are generically referring to this open source software platform that you call it Jakarta EE rather than EE4J. EE4J, the Eclipse Top-level project,  is the only name we’ve had for a couple of months, but as we at least tried to make clear, that was never intended to be the brand name.

Update: Fixed a typo plus the formatting of the Glassfish row in the translation table.
Update 2: [*] To be clear, the Java Community Process will continue to exist and to support the Java SE and ME communities. However, it will not be the place where Jakarta EE specifications will be developed.
Update 3: Corrected the name of the working group from EE.next to Jakarta EE.

Written by Mike Milinkovich

February 26, 2018 at 2:00 pm

Posted in Foundation

Tagged with , ,

EE4J Code Arrives

Last week the EE4J project achieved an important milestone when the source code for the API and reference implementation of JSON-P JSR-374 project was pushed by Dmitry Kornilov into its GitHub repository in the EE4J organization. This is the first project of the initial nine proposed to reach this stage.

This may seem like a small step in a very large process, but it is a concrete demonstration of the commitment to move forward with the migration of Java EE to the Eclipse Foundation. The Oracle team and the Eclipse Foundation staff had a ton of work to do to make this possible. This is definitely one of those cases where the visible code contributions are just the visible tip of an iceberg’s worth of effort.

Here are just a few examples of the work that went on to get to this stage:

  • The names of the projects such as Glassfish represent important trademarks in the industry. Oracle transferred ownership of these project names to the Eclipse Foundation so that they can be held and protected for the community.
  • The EMO staff reviewed the projects proposals, ran the project creation review, provisioned the repositories and set up the committer lists.
  • The Oracle team packaged up the source code and updated the file headers to reflect the new EPL-2.0 licensing.
  • The EMO IP staff scanned the code and ensured that all was well before approving it for initial check-in.

Now that the collective team has run through this process with JSON-P we will be working to get the remaining eight initial projects pushed out as quickly as possible. Hopefully by the end of this month. Meanwhile, more projects will be proposed and we will be migrating a steady stream of Java EE projects into EE4J.

Exciting times!

Written by Mike Milinkovich

January 15, 2018 at 11:51 am