#Eclipse development kit software#
This vision will go a long way towards ensuring the software remains relevant, sustainable, and high quality as it evolves.Ī review of the Eclipse IDE Simultaneous Release schedule highlights the need for continued sustainability due to declined activity of new features from the about 70 sub-projects. The future of the Eclipse IDE family of projects will be based on a strong, shared vision. They will also oversee the related planning, delivery processes, and delivery technologies for the software suite. will provide governance support, guidance, and funding to the communities that deliver and maintain the Eclipse IDE software components. While the Eclipse newsletter didn't explicitly answer these questions, the message was clear: It was quite an agile project that delivered specifications at quite a quick pace.Īccording to the Jmeeting minutes, the Eclipse IDE WG planned to both provide a "clear statement on the motivation of why the working group is important" and to answer the questions of "Why now? " and "The IDE project has been there for so long, so what is different?"
Historically, MicroProfile moved quickly with minimal process and late-binding decisions. So, there are more legal protections in place now that MicroProfile is a Working Group.Ī working group also places more processes on MicroProfile.
#Eclipse development kit driver#
The primary driver behind creating the MicroProfile Working Group is to close intellectual property gaps identified by the Eclipse Foundation for specification projects. When asked about the benefits of MicroProfile creating a working group after four years of working independently, John Clingan, senior principal product manager at Red Hat, told InfoQ: We believe that the core values that have been part of MicroProfile since its very beginning, like a lightweight process, vendor-neutrality, transparency, accountability, innovation, and implementation first, are the keys to the project's success. In these last 4+ years, the MicroProfile community has grown beyond the most optimistic expectations. Roberto Cortez, SmallRye project lead at Red Hat, provided a retrospective on the previous work by the MicroProfile community, writing: However, the MicroProfile WG, having joined the Eclipse Foundation in December 2016, was completed in October 2020. The Jakarta EE, OSGi, and Adoptium working groups were created shortly after joining the Eclipse Foundation.
Over the past few years, a number of Eclipse Foundation working groups have been established. The Java community may be wondering why the Eclipse Foundation is requiring the creation of an Eclipse IDE working group after 17 years of operating independently. We believe the IDE needs to be more relevant and attractive for end users, committers, tool developers, and those who build applications upon it. Renesas are keen to invest in the Eclipse IDE working group to ensure the platform stays relevant and maintainable into the future. The working group also "promotes the 'Eclipse IDE' brand and its value in the marketplace, provides vendor-neutral marketing", and "leverages Eclipse Foundation licensing and intellectual property flows."įounding organizations of the Eclipse IDE WG include Bosch, EclipseSource, IBM, Kichwa Coders, Renesas, SAP, VMware, and Yatta Solutions.Īkiya Fukui, vice president, Software Development Division, IoT and Infrastructure Business Unit at Renesas Electronics Corporation, discussing the importance of this new working group, stated: 17 years after the initial release of the Eclipse IDE, the Eclipse IDE Working Group (WG) was established to ensure its "continued sustainability, integrity, evolution and adoption." According to its charter, the working group establishes and drives funding, oversees the release plan, coordinates the simultaneous releases, helps to grow and evolve the ecosystem and Eclipse Marketplace, and provides governance for related open source projects.