Skip to main content
2018 Annual Eclipse Community Report

2018 Annual Eclipse Foundation Community Report

Published June 2018

Welcome to the seventh annual Eclipse Foundation Community Report. Comments and feedback on the style and content would be appreciated at

Except where noted this report will cover the period April 1, 2017 to March 31, 2018.

Who We Are

The Eclipse Foundation’s mission is summarized as follows:

The Eclipse Foundation’s purpose is to advance our open source software projects and to cultivate their communities and business ecosystems.

This makes the Eclipse community a unique open source community. Not only are we interested in building open source code and community, but we are equally committed to creating a commercially successful ecosystem around that code. This combination of interests has been a key part of Eclipse's success.

In short, our vision for the Eclipse community is

To be the leading community for individuals and organizations to collaborate on commercially-friendly open source.


The following are the strategic goals of the Eclipse Foundation for 2018, as established by the Board of Directors.

  1. Be a leading open source community for emerging technologies. This remains as one of the continuous objectives of the Foundation. The Eclipse Foundation staff and leading members of our community seek to attract projects and members in emerging technology domains.
  2. Cultivate the growth of our projects, communities, and ecosystems. The creation of a large community of commercial and open source organizations that rely on and/or complement Eclipse technology has been a major factor in the success of Eclipse. Each time Eclipse technology is used in the development of a product, service, or application, the Eclipse community is strengthened. Our goal in 2018 is to continue to focus our attention on the success of our working groups and on new Eclipse projects that focus on particular industry segments such as IoT, web development, mobile, automotive, science, and finance. The decision announced in September 2017 by Oracle to move the Java EE platform to Eclipse Foundation represents a significant contribution to the Foundation. In total, more than 40 new projects are in the process of being migrated to the Foundation; this migration includes the engagement of a wide cross-section of both existing and new members.
  3. Create value for all its membership classes. The Eclipse Foundation serves many members whose primary interest is leveraging Eclipse technologies in proprietary offerings such as products and services. The Eclipse Foundation continues to focus its energies to ensure that commercial opportunity exists within the Eclipse ecosystem. Committers are also members of the Eclipse Foundation and are in many ways its backbone. Over the past year, improvements to the common build infrastructure (CBI) have been undertaken to provide more robust and extensible build infrastructure to the key projects of interest to our members. Improvements and enhancements have also been made to our development and intellectual management processes, and the Foundation’s Architecture Council has recently begun a major review of the Eclipse Development Process, which is the cornerstone used by all our projects.
  4. Be the leading community for developer tools. A goal of the Eclipse Foundation is to define development platforms that are freely licensed and open source, and that provide support for the full breadth of the application lifecycle in many disparate problem domains and across the development and deployment platforms of choice, including embedded, desktop, and the web. Increasingly, support for multiple languages has also become a focal point. The Eclipse community is best known for its desktop IDEs such as the Eclipse Java development tools (JDT) and the C/C++ development tools (CDT). However, under the leadership of the Eclipse Cloud Development top-level project, the Eclipse Che, Eclipse Dirigible, Eclipse Orion, and just recently Eclipse Theia projects are working on new tooling platforms for cloud-based and web development.
  5. Increase our membership revenue. Aligned with the four strategic goals listed above is an explicit goal to increase the revenue generated directly from membership. Specifically, the goal is to both increase the number of new members as well as to increase the revenues from existing members by demonstrating to members the value to them of increasing their level of membership. In early 2018, the Jakarta EE Working Group was established, and has led to three new strategic memberships in the Foundation. There is also a renewed effort to engage more enterprise organizations as members. Also related to membership, the Foundation introduced in late 2017 Member Funded Initiatives as a means for members, either directly or in collaboration with other members, to engage with the Foundation to fulfill specific objectives of importance to the member(s).

Some Key Decisions

Over the past year, the Board has made a number of strategic decisions that will impact how Eclipse evolves in the future. A brief summary of these is listed below. More details can be found in the minutes of the Board, found on our website.

  • Approval and adoption of Eclipse Public License 2.0. In August, 2017, the Board approved the Eclipse Public License 2.0, and also approved the adoption of the EPL v2.0 as the Foundation’s default software license. The EPL v2.0 was also certified as a free and open source license by the Free Software Foundation and the Open Source Initiative.
  • Updates to the Foundation’s Anti-Trust Policy. In October, 2017, the Foundation made updates to the Anti-Trust Policy. All members are encouraged to ensure they are familiar with the terms of this Policy.
  • Creation of EE4J Top Level Project. The Board approved the creation of the Eclipse Enterprise for Java (EE4J) top level project in October, 2017. This top level project is the top level project for the 40+ projects being brought to the Foundation as part of the donation by Oracle of Java EE to the Foundation. The Executive DIrector subsequently approved the creation of the Jakarta EE Working Group in March, 2018, which is the working group focused on the successful transition of Java EE to the Foundation, and to drive the new Jakarta EE brand forward.
  • Adjustment of Annual Enterprise Membership Fees. In January, 2018, the Board adjusted the annual membership fees associated with the Enterprise Membership in the Foundation. The move was made to make the Enterprise Membership level of membership more attractive to Enterprises.
  • Adoption of CloudBees Jenkins Enterprise. In February, 2018, the Board supported the EMO’s proposal to adopt CloudBees Jenkins Enterprise for use by staff and project committers. The adoption of this technology paves the way for the Foundation to improve and enhance its Common Build Infrastructure, and is expected to be rolled out in the third quarter of 2018.


As of April 30, 2018, the Eclipse Foundation has twelve (12) strategic members, including CA Technologies, CEA List, Fujitsu, IBM, itemis AG, Obeo, Oracle, Payara Services, Red Hat, Robert Bosch GmBH, SAP, and Tomitribe.

Of note, the Eclipse Foundation also counts over 1500 committers. Committers are entitled to membership in the Foundation, and play a valuable role in the Eclipse Foundation governance, including representation on the Eclipse Board and many working group steering committees.

The Foundation finished 2017 with 270 member companies. By the end of April 2018, that number increased to 274 member companies. A total of 34 new companies joined as new members of the Foundation from May 1, 2017 through April 30, 2018, including

ADLINK Technology Inc., Astraea Inc, Baloise Holding AG, BTC Business Technology Consulting AG, Calypso Networks Association, Castalia Solutions, CloudBees Inc., Cloudera Inc, Contact Software GmbH, Enalean SAS, Fujitsu Limited, GFOSS - Open Technologies Alliance, Hazelcast Inc, InfluxData, JavaPro, JNBridge, LLC, Kynetics, Lightbend Inc, M3S Research Unit at the University of Oulu, Merantix GmbH, Mindus SARL, Nanjing Glaway Software Co. Ltd, Orange S.A., Pacific Northwest National Laboratory (PNNL), Paranor Engineering AG, PRFC, Skymind Inc., The University of York, toem GmbH, Tomitribe Corporation, TUEV SUED Auto Service GmbH, University of L' Aquila, University of Zagreb Faculty of Electrical Engineering and Computing (FER), V2COM.

Working Groups

The recruitment of new projects and members has been greatly assisted by the strategy of creating Eclipse working groups. As participation in working groups grows, our membership has grown and diversified into different industries such as automotive, aerospace, geospatial, and the Internet of Things.

Internet of Things (IoT) The Eclipse IoT Working Group is a community of organizations and individuals building open source technology that is used to build IoT solutions. Eclipse IoT has 34 different open source projects and 42 working group members. The technology portfolio include technology for embedded constrained devices, IoT gateways, and IoT cloud platforms.

New members of the Eclipse IoT Working Group in the past 12 months include: ADLINK Technology, Cloudera, CONTACT Software, DB Systel, InfluxData, Intel, Kichwa Coders, Nokia, Orange, SAP, V2COM

A number of new projects joined the Eclipse IoT community in the past year, including

  • Eclipse Mita, a new programming language for embedded IoT devices;
  • Eclipse Thingweb, an implementation of the Web of Things standard from the World Wide Web Consortium (W3C);
  • Eclipse Cyclone DDS, an implementation of the OMG Data Distribution Service (DDS) standard;
  • Eclipse Duttile, an open and shared Agile/Lean methodology that links the tools and utilities available in the Eclipse IoT ecosystem;
  • Eclipse Kuksa, a cloud platform that interconnects a wide range of vehicles to the cloud via in-car and internet connections;
  • Eclipse HIP, a Hierarchical IoT Protocol (HIP) designed to increase the scalability and interoperability of large scale IoT deployments;
  • Eclipse fog05, a project that aims at providing an open source, scalable, fog computing platform, to virtualize concerns like “compute,” “storage,” and “communication.”

In an effort to provide integrated “stacks” of IoT frameworks and runtimes, a new sub-committee of the IoT Working Group focusing on integration topics was formed at the end of 2017. It is tasked with facilitating cross-project communication and synchronization of the Eclipse IoT projects’ roadmaps and APIs.

The Eclipse IoT Working Group continues to undertake a number of community outreach and development programs, including the following:

  • In April 2017, Eclipse IoT launched a new “Open IoT Testbeds” program. These testbeds are collaborations between vendors and open source communities such as Eclipse to demonstrate and test commercial and open source components needed to create specific industry solutions. Two testbeds (Asset Tracking Management, and Production Performance Management) were released in 2017, and it is expected more testbeds will be created in 2018.
  • Eclipse IoT Days were hosted in San Jose, USA; London, UK; Ludwigsburg, Germany; and Grenoble, France.
  • The Open IoT Challenge attracted 78 proposals to build IoT solutions based on open source and open standards.
  • In April 2017, the WG published the results of the third IoT Developer Survey. The results of this survey have been viewed over 45,000 times on Slideshare. Like in previous years, the survey is often referenced and quoted in the industry.
  • The Eclipse IoT Working Group published a new white paper titled Open Source Software for Industry 4.0.
  • Eclipse IoT supported and promoted its members through participation at several trade shows, including: IoT Solutions World Congress, Red Hat Summit, IoT World, Bosch Connected World, etc.
  • Two new case studies were published, showcasing what companies are building with Eclipse IoT Technology.

LocationTech, hosted by the Eclipse Foundation, is a working group developing technologies with spatial awareness. Now in its fifth year, LocationTech includes 18 members and 13 projects. During the past 12 months, a number of major milestones were achieved, besides significant releases by a number of projects, a first simultaneous release was made.

Strategic members of the LocationTech working group include Boundless, IBM, Oracle, and Red Hat. Participant solutions members include: Astraea (joined as new member), Azavea, CCRi, OGC, Planet, RadiantSolutions, SensorUp, Terranado, and VividSolutions.

Alll key projects (LocationTech GeoWave, LocationTech GeoGig, LocationTech GeoTrellis, LocationTech GeoMesa and LocationTech JTS) were incorporated in the first LocationTech simultaneous release in November 2017.

LocationTech was prominently represented at FOSS4G Global 2017 in Boston, the largest global open geospatial conference. The working group and its members and projects were represented in all aspects of the program: talks, BOFs, workshops, code sprint, exhibition area, and B2B sessions. On a regional level, LocationTech co-organized with URISA the CalGIS 2017 conference in May in Oakland, in support of its members and community. A large part of the program was dedicated to featuring the various LocationTech projects.

The Science Working Group (SWG), hosted by the Eclipse Foundation, works to solve the problems of making science software interoperable and interchangeable. It was founded in June 2014 and is now in its third year of operation. The Science working group has grown to 15 members and 10 projects. This report covers the period from March 2016 to March 2017.

The group has the following members:

  • Steering Committee members: Diamond Light Source, IBM, Itema, Kichwa Coders and Oak Ridge National Laboratory
  • Participating members: Airbus, Clemson University, IFP Energies Nouvelles, iSencia Belgium, Lablicate, Open Analytics, Skymind (new member), Soleil Synchrotron, Tech’Advantage Group, The Facility for Rare Isotope Beams and Uppsala University

In its fourth year, the following projects joined the working group:

  • Eclipse Apogy provides a set of frameworks, Eclipse EMF models and Graphical User Interface components that simplify the creation of the software required to operate a physical system.
  • Eclipse Deeplearning4J provides a core set of components for building applications that incorporate AI and targets enterprises looking to implement deep learning technologies.
  • Eclipse XACC is a programming framework and specification enabling quantum acceleration in existing classical computing in a manner that is language and hardware agnostic.

The group hosted an Unconference at EclipseCon France in June 2017 with a special workshop dedicated to the Eclipse January project. During the conference eight talks for the Science track were presented.

Also in October 2017, the group coordinated their annual common release for some of its projects. The aim was to make the working group more visible and ensure that some of the projects depending on each other were synchronized. A joint press statement was released by the Eclipse Foundation and Oak Ridge National Labs on the topic of the release.

At EclipseCon Europe 2017, Tracy Miranda gave an overview of the activities and projects of the Eclipse Science Working Group under the title “Science@Eclipse.” The group also participated in the Unconference prior to the conference.

In August 2017 the XACC project was featured in the Eclipse Newsletter.

The Eclipse Long-Term-Support Working Group has become inactive. It is the Foundation’s intention to dismantle the Eclipse Foundation hosted LTS infrastructure in the second quarter of 2018.

The Eclipse openMDM (measured data management) Working Group wants to foster and support an open and innovative ecosystem providing tools and systems, qualification kits, and adapters for standardized and vendor independent management of measurement data in accordance with the ASAM ODS standard.

Since May 2017, the openMDM working group has changed its development effort. The Eclipse Foundation has been tasked to contract a product manager as well as a standing development team funded by the working group. While a few IP issues and code refactoring was holding up the team, good progress has been made. Regular milestone releases are taking place and the working group is targeting a major release in the summer of 2018. The ASAM ODS based software stack is now tested by various German OEMs and product companies and is likely to go into productive environments in 2018.

openMDM technology is expected to become part of the Eclipse openADx initiative.

The PolarSys Working Group focuses on providing open source development solutions for Software and Systems Engineering. It has 25 members and 18 projects hosted on the PolarSys forge. New members in the period include Glaway Software, PRFC, Malardalen University and University of York.

During the past 12 months, PolarSys members continued to improve the PolarSys established solutions (Capella and Papyrus) with a focus on product management and usability. PolarSys participated to several conferences, including Incose Symposium, Models 2017, and Euroforum in order to promote these solutions.

Airbus submitted a new project, PolarSys libIMS, the reference implementations of a standard middleware that serves as a guide for interconnection of modules (software or hardware) with avionic test benches. Polarsys B612, the open source font designed for readability, received the Industry award from “L’Observeur du design” and was references by several font referencing websites. OpenCert and CHESS benefited from new efforts in the context of the AMASS european research project to create an open platform for safety assurance and certification processes.

During the year, PolarSys members dedicated some effort to improve SWTBot, and to start the definition of a PolarSys release train as a way to enable medium-term support (~3 years) for the PolarSys solutions.

This period was also the second year of operation of the Papyrus Industry Consortium, a PolarSys hosted industry consortium (IC) of 15 members dedicated to the advancement of the Papyrus ecosystem. The Papyrus IC sponsored exhibit booths at different conferences including EclipseCon France, Models 2017, EclipseCon Europe, and Euroforum. All the committees of the Papyrus IC were active this year including the Steering Committee, the Architecture Committee, the Product Management Committee, and the Research Committee. The Product Management Committee continued its effort to organize Papyrus Industry consortium Product Line and to design streamlined version of the Papyrus tool platform; the Papyrus for Information Modeling was improved, and the plans for Papyrus UML Light and Papyrus SysML were defined. Finally, the consortium decided to fund the support of UML2 to make sure that this foundation component is included in Eclipse Photon, and to ensure a transition to a management of this component by a larger part of the community.

In June 2017, PolarSys members created the Capella Industry Consortium to foster the development of the Capella ecosystem. The Capella IC has 6 members and welcomed Glaway Software, the first PolarSys member from Asia in January 2018. During the predio, the Capella IC participated to several events, including a Capella Day (co-located with EclipseCon France) as a launch event, Incose Symposium, Euroforum, and ERTS. The Capella IC also organized several webinars that attracted more than 350 participants from more than 130 organizations.

The Eclipse openPASS Working Group was initiated in August 2017 by three German car manufacturers: BMW, Daimler, and Volkswagen.

The rise of advanced driver assistance systems and partially automated driving functions leads to the need of virtual simulation to assess these systems and their effects. This especially refers, but is not limited, to safety effects in traffic. There are various methods and tools for prospective evaluation of safety systems with respect to traffic safety. Implementing the methodology by creating and maintaining the SIM@openPASS platform will support reliability and transparency of results obtained by simulation. The growing number, complexity, and variety of those vehicle functions make simulation an essential part in research, development, testing, public rating, and homologation and is thus, directly or indirectly, required by all stakeholders in vehicle safety, including manufacturers, suppliers, insurance companies, legislators, consumer advocates, academia.

The Eclipse openPASS Working Group is the driving force behind related development of core frameworks and modules. The Eclipse openPASS WG endeavors to make sure that openPASS related Eclipse projects are in line with external important developments. The goal is a broad availability of different modules.

Work on the related Eclipse simopenpass project started immediately after the creation of the working group and was mostly executed by the fourth founding member, the Munich based company ITK Engineering GmbH. While there are still issues with the existing code base, the car manufacturers have started installing and using the code base. A milestone release is now available, and development and contributions from various company continue.

For the future, we expect code consolidation and growth of the related ecosystem.

In January 2018, the German TÜV Süd joined the openPASS Working Group.

openPASS technology is expected to become part of the Eclipse openADx initiative.

Conferences and Events

The EclipseCon conferences, Eclipse Days, and DemoCamps are the primary events that the Eclipse Foundation supports to help foster the strong personal relationships in the community that only face-to-face contact can create. We highly encourage all Eclipse community members to participate in one or more of these events.

EclipseCon France was held in June 2017 and had 250 attendees. The conference returned to its original format as a full two-day event. The Unconference, always well attended at EclipseCon France, was held at a new location, and again was well attended. The conference was held during a significant heat wave in Toulouse, and was run at the same time as the annual Fête de la Musique festival that runs throughout Toulouse.

EclipseCon Europe celebrated its twelfth anniversary in October 2017, with 609 people in attendance. This event was co-located with the OSGi Community Event, and included a great collection of technical sessions, BoFs, the IoT Playground, and included a fascinating talk by Roberto Di Cosmo of INRIA about their project to build “a universal software knowledge base”. The conference also hosted a number of dedicated events, including the IoT Day, the CDT Summit, and Project Quality Day. Feedback from the conference from both attendees and sponsors continues to be very strong, with many stating this was the best EclipseCon conference yet.


The Eclipse Foundation’s fiscal year end is December 31. Our auditors are the firm Deloitte & Touche, LLP. The Eclipse Foundation is incorporated in the State of Delaware, USA as a 501(c)6 not-for-profit. Our headquarters are located in Ottawa, Canada. The Eclipse Foundation also has a wholly-owned German subsidiary, Eclipse Foundation Europe GmbH.

Membership renewals remained strong, and working group revenue and website advertising were both steady compared to 2016. The organization continues to be on a solid financial footing, and the migration of Java EE to the Eclipse Foundation represents an opportunity for new membership growth. The financial impact of strategic membership is always significant to the Foundation. We were pleased to have Fujitsu, Payara Services, and Tomitribe all join as strategic members in the first four months of 2018, largely due to their participation in the new Jakarta EE working group. This counterbalanced the impact of Ericsson changing their membership from Strategic to Solutions members, and Codenvy’s ceasing as a strategic member due to their acquisition by Red Hat in June, 2017.

Looking forward to 2018, the Board has approved a budget forecasting a $0.2M loss.

In US $ millions 2014 2015 2016 2017 2018 Budget
Revenue 4.3 4.9 5.4 5.6 6.5
Expenses 4.7 4.0 5.6 5.7 6.7
Net Income (0.4) 0.0 (0.2) (0.1) (0.2)

Marketing and Brand Management

Oxygen Launch

  • A new Oxygen landing page was created to promote the 12th annual simultaneous release from the Eclipse community.
  • As part of the launch, six webinars were produced and recorded to promote some of the projects included in the Oxygen release. The series was well received with over 30,000 Youtube views from launch in June 2017 to March 2018.

Eclipse Foundation Brand Evolution

  • The Eclipse Foundation conducted a community brand perception survey in Q2 2017. The goal was to test the perceived meaning of the Eclipse brand within our community and the greater developer community. The results were presented to the Board and the general membership meeting.
  • A new Eclipse Foundation logo was produced in March 2018 to create a visual identity distinct from the Eclipse projects, notably the Eclipse Platform and Eclipse JDT. The logo was unveiled in April 2018.
  • In conjunction with the introduction of the new Eclipse Foundation logo, a redesigned website was launched in April 2018. The scope of work completed included an updated look and feel for the site, as well as new content focused on better explaining the Foundation’s overall mission and the role of working groups within the Eclipse ecosystem.

Jakarta EE

  • The Foundation and Jakarta EE working group developed and executed a major press and analyst relations campaign to promote the Jakarta EE brand including a new Jakarta EE logo, the formation of the Jakarta EE working group, and the results of an enterprise Java developer survey conducted by the Foundation. The Foundation engaged Flak42, an expert press and analyst firm, to assist in the campaign.
  • The website was launched on April 24, 2018, and is intended to be the primary site for all activities related to the Jakarta EE community, as well as the working group.
  • The Jakarta EE name was chosen through a community vote that saw over 7,000 votes cast. The graphic for the logo was also chosen by community vote that saw over 2,000 votes cast. Both of these participation rates were significant, and the relatively fewer votes seen for the graphic are largely attributed to the voting process was more involved as there were additional choices to be made.

Simultaneous Releases for both Science and LocationTech Working Groups

  • Both the Science and LocationTech working groups implemented simultaneous releases of their projects in September and November, 2017 respectively. Both working groups used these simultaneous releases as a focal point for driving awareness and interest in key projects. Both plan on making this an annual activity, similar to the Eclipse IDE’s annual release.

Ongoing Marketing Research

  • The Marketing team has been working to engage the community on behalf of our member organizations to find out insights on the marketplace.
  • A survey of over 1,800 Jakarta EE developers was carried out, with results aligning with the objectives and vision statement of the Jakarta EE working group.
  • The fourth annual IoT developer survey was conducted. The survey of over 500 individuals yielded insights on IoT solution trends, challenges and opportunities.


  • The Virtual Eclipse Community Meetup (vECM) series was launched and was well received. The vECM recordings received over 32,367 views from April 2017 to March 2018.

Social Media

  • Our YouTube channel experienced strong growth with total views up by 53% from April 2017 to March 2018. During the same period, YouTube subscribers grew by 27%.
  • The Foundation’s presence on Twitter, Facebook, and LinkedIn experienced positive growth over the year: Twitter Followers +29%, Facebook Likes +2% and LinkedIn Group Members +3%.

Eclipse Newsletter

  • The Eclipse Community Newsletter continues to grow in popularity. The total number of subscribers grew by 26% to reach 233,000 total subscribers in March 2018.

Intellectual Property Management

During the time period spanning April 1, 2017 to March 31, 2018, the Eclipse Foundation received 2,926 requests for intellectual property review and completed 2,499 reviews. This represents a massive spike in the demands made on the Eclipse IP Team over the previous period (1,933 and 1,894 respectively).

The Eclipse Intellectual Property Policy was updated in 2016 to include two types of IP Due Diligence for the third-party software used by open source projects hosted by the Eclipse Foundation. Type A Due Diligence involves a license certification only and Type B Due Diligence provides our traditional license certification, provenance check, and code scan for various sorts of anomalies. Prior to this change, project teams would have to wait until the full application of what we now call Type B Due Diligence was complete before issuing a release. Now, a project team can opt to push out a Type A release after having all of their third-party libraries license certified.

Project teams appear to be enthusiastically taking advantage of this new type of due diligence. The rate by which requests for Type B reviews arrive appears to have dropped somewhat over the last two reporting periods, but still remains very strong (the statistical trend is still upwards) while the adoption of Type A is spiking.

Third party review requests (CQs) created by report year (April to March)

As of the end of March 2018, we have 59 projects using Type A IP Due Diligence. All new projects are being directed to employ Type A Due Diligence for all incubation releases and encouraged to defer the decision whether or not to switch to Type B (license certification, provenance check, and code scan) until graduation. There is, of course, no specific requirement to switch at graduation or ever, but we are actively encouraging project teams to defer the decision of whether or not to switch from Type A until at least that point.

Top users of Type A Third Party Due Diligence (Apr 2017 to Mar 2018)

The Eclipse IoT and Technology Top Level Project together accounted for more half of the intellectual property reviews initiated between April 1, 2017 and March 31, 2018. This aligns well with the rates of new project creation in those Top Level Projects (approximately 65% of all new projects created in in that time frame were created under Eclipse Technology and Eclipse IoT Top Level Projects).

CQ Created by Top Level Project between April 1, 2017 and March 31, 2018)

As the primary incubator for new projects, it’s natural that the Eclipse Technology Top Level Project is the leading source of requests for intellectual property review. The breakdown by project shows a great deal more diversity than in previous years (while the Eclipse Technology Top Level Project accounts for most of the IP reviews, only two Eclipse Technology Projects are in the top top ten consumers).The Eclipse Keti (IoT) project stands out as the high consumer of intellectual property resources. The rapid growth of the IoT project space continues to translate into high individual project representation in the “top-ten” consumers of intellectual property resources.

CQs created by Projects between April 1, 2017 and March 31, 2018


Photon Simultaneous Release

In June 2017 the Eclipse community shipped Eclipse Oxygen, its twelfth annual simultaneous release. Including previous releases of the Eclipse Platform, this was the fourteenth release that was shipped on time, to the day. A total of 83 projects participated in the Oxygen simultaneous release. The release comprises 71 million lines of code produced by 283 committers from 46 member companies, with contributions from 417 non-committer contributors.

Simultaneous Release Metrics (current year final numbers pending)

Six projects joined the Eclipse Photon Simultaneous Release: the Eclipse aCute and Eclipse TM4E projects add support for C# language and TextMate® grammars to the Eclipse IDE; the Eclipse RedDeer project adds new options for testing SWT and RCP applications; and the Eclipse Collections, EclipseLink, and Eclipse Yasson projects add new runtimes.

The project teams from Eclipse EGerrit, Eclipse Sphinx, Eclipse Orion, and Eclipse Subversive SVN Team Provider decided to drop out of the simultaneous release. Perhaps the biggest implication of this list of dropped projects is that it is no longer possible to provide out-of-the-box support for SVN. In practice, none of our packages include this support anyway, so developers who require that functionality must go to Eclipse Marketplace to add it; these developers will likely find an alternative such as SubClipse.

This predictable release schedule has been a key part of the Eclipse Community's success over the years, and is an important part of the success of the Eclipse ecosystem.


The number of proposals that we receive year-after-year is on an upward trend. We’re off to a very good start in 2018, having received 27 new project proposals in 2018Q1.

New Project Proposals by Year

The following projects were proposed at the Eclipse Foundation in 2017:

  • Eclipse Ditto provides a ready-to-use functionality to manage the state of Digital Twins.
  • Eclipse XACC provides the software interfaces and infrastructure required by domain computational scientists to offload computationally intractable work to an attached quantum accelerator.
  • Eclipse aCute project provides development tools for C# and .NET Core applications in the Eclipse IDE.
  • Eclipse BaSys 4.0 develops a basic system (similar to AUTOSAR) for production plants that implements the efficient reconfiguration of production processes.
  • Eclipse Bridge.IoT enables harmonization across IoT platforms, along with an IoT marketplace for platforms and services as providers to trade available resources.
  • Eclipse Ceylon encompasses development of the Ceylon language itself, the compiler frontend, the compiler backends for Java and JavaScript, the module system, the command-line tooling, the SDK, and the Eclipse-based IDE.
  • Eclipse CogniCrypt produces a set of Eclipse Platform plug-ins that assist developers with the generation of secure crypto-integration code; perform static analysis of existing crypto-integration code; suggest better/more secure integrations via quick fixes; and alert developers of security breaches of cryptographic algorithms.
  • Eclipse Cyclone implements the OMG Data Distribution Service (DDS) specification and the related specifications for interoperability.
  • Eclipse Deeplearning4J facilitates building deep learning applications covering the whole lifecycle of building deep learning products from data preprocessing to deployment.
  • Eclipse Duttile produces a shared Agile/Lean methodology that links the tools and utilities available in the Eclipse IoT ecosystem.
  • Eclipse eLogbook@openK provides a digital logbook for Distribution System Operators (DSO).
  • Eclipse Grizzly NIO framework has been designed to help developers to take advantage of the Java™ NIO API.
  • Eclipse IoT-Testware supports conformance, interoperability, robustness, and security testing of IoT devices and services via TTCN-3 test suites and cases.
  • Eclipse Jersey is a REST framework that provides the reference implementation for JAX-RS, and extends the toolkit with additional features and utilities to further simplify RESTful service and client development.
  • Eclipse Kuksa unifies technologies across the vehicle, IoT, cloud, and security domains in order to provide an open source ecosystem to developers addressing challenges of the electrified and connected vehicle era.
  • Eclipse Mita provides a new programming language for the embedded IoT including editor/IDE, compiler and an extensive test-suite.
  • Eclipse Mojarra is the Reference Implementation for JavaServer Faces (JSF), a Java specification for building component-based user interfaces for web applications.
  • Eclipse OpenJ9 is a high performance, enterprise calibre, flexibly licensed, openly governed cross platform Java Virtual Machine.
  • Eclipse OpenMQ (Open Message Queue) is a complete message-oriented middleware platform, offering high quality, enterprise-ready messaging.
  • Eclipse Ozark provides an implementation of action-based MVC specified by MVC 1.0 (JSR-371). It builds on top of JAX-RS and currently contains support for RESTEasy, Jersey, and CXF with a well-defined SPI for other implementations.
  • Eclipse Picasso provides a web application written in Python for rendering standard visualizations useful for training convolutional neural networks.
  • Eclipse Project for JAX-RS provides a Java programming language API spec that provides support in creating web services according to the Representational State Transfer (REST) architectural pattern.
  • Eclipse Project for JMS (Java Message Service) provides a Java Message Oriented Middleware API for sending messages between two or more clients.
  • Eclipse Project for JSON Processing (JSON-P) is an API to process (e.g. parse, generate, transform, and query) JSON documents.
  • Eclipse Project for WebSocket specifies the API that Java developers can use when they want to integrate WebSockets into their applications.
  • Eclipse SCAVA assembles a knowledge base of data collected from open-source repositories (code version management systems, issue trackers, continuous integration systems, and discussion forums in natural language) that is used to query for specific answers when the programmer is confronted with (a) a design decision or (b) a code or design smell.
  • Eclipse SUMO provides an open microscopic and mesoscopic traffic simulator.
  • Eclipse TEA is a tasking orchestration engine that can be run from within the Eclipse IDE or headlessly.
  • Eclipse Thingweb provides an open-source toolkit for the Web of Things ecosystem with modular implementations of the technological building blocks standardized by the W3C.
  • Eclipse Tyrus provides a reference implementation for Java API for WebSocket.
  • Eclipse Xpect supports testing Xtext languages and the process of designing such languages.
  • Eclipse Xsemantics provides a DSL for writing rules for languages implemented in Eclipse Xtext.
  • Eclipse GEMOC Studio offers a framework for designing and integrating EMF-based modeling languages.
  • PolarSys LibIMS provides a fully open-sourced reference implementation of the Eurocae ED-247 specification.
  • Eclipse RedDeer is an extensible framework used for development of automated SWT/Eclipse RCP tests that interact with application’s user interface.
  • Eclipse sensiNact builds a software platform enabling the collection, processing, and redistribution of data relevant to improving the quality of life of urban citizens.
  • Eclipse SystemFOCUS is an IDE that targets fast and meticulous development of embedded software.


Since 2013, the Foundation increased its collaboration with academics, researchers, and industries by participating in several European projects. The Foundation’s main objective in these projects is to help the consortium engaged in each project build an open source platform and community around their respective EU research project.

The positive side effects are

  • Eclipse Foundation’s recognition as an expert in building open source communities
  • The opportunity to bring new academic and industrial members to the Foundation
  • The opportunity to promote and disseminate existing Eclipse projects into such international consortia

As of March, 2018, Eclipse Foundation Europe is a research partner in seven large European research projects.

  • Amalthea4Public: Started in fall 2013. This project is implementing an Open Platform for Embedded Multicore Systems. This project will be winding up in the fall of 2018.
  • AGILE-IoT: Started in January 2016. This implementation is building an Adaptive & Modular Gateway for the Internet of Things (IoT).
  • AMASS: Started in April 2016. This project is creating an open tool platform, ecosystem, and self-sustainable community for assurance and certification of Cyber-Physical Systems (CPS) in the largest industrial vertical markets including automotive, railway, aerospace, space, energy.
  • BaSys 4.0: Started in fall 2016. The goal of BaSys 4.0 is the creation of an Industry 4.0 base system for factories to ensure efficient transformations in the production processes.
  • Crossminer: Started in January 2017. CROSSMINER enables the monitoring, in-depth analysis, and evidence-based selection of open source components, and facilitates knowledge extraction from large open-source software repositories.
  • RobMoSys: RobMoSys envisions an integrated approach built on top of the current code-centric robotic platforms, by applying model-driven methods and tools.
  • Appstacle: Started in April 2017. APPSTACLE stands for open standard APplication Platform for carS and TrAnsportation vehiCLEs. Appstacle aims to establish a standard car-to-cloud connection, open for external applications and the use of open source software wherever possible without compromising safety and security.

Eclipse Foundation Europe also created a research consortium named GEMOC. This open and international initiative aims to coordinate and disseminate the research results regarding the support of the coordinated use of various modeling languages that will lead to the concept of the globalization of modeling languages.

Committer and Project Community

Our number of committers grew past 1,500 in early 2018.

The EMO is committed to providing a robust and dependable server and software infrastructure, including professional support staff to assist projects and working groups in achieving their goals effectively and efficiently, as well as steadily improving services to the Eclipse committers and the projects they work on. Here is a sampling of some infrastructure metrics, plus some improvements we've put into place over the past year.

  • Servers and Infrastructure: Core service availability (Git,, and Bugzilla) for 2017 was 99.983%, up from 99.958% in 2016. A recurring pattern of rapid incoming download requests, every Tuesday night, transformed itself into a non-malicious DDoS attack and exposed the age, and capability limits of our load balancers and firewalls. New hardware has been acquired and will be provisioned in 2018. Also, stability issues with Nexus and our database systems were addressed early in the year.
  • Common Build Infrastructure: In 2017 we began phasing out Hudson in favour of Jenkins as the CI tool of choice. We’ve also planned for the deployment of clusterized and pipelined CI/CD, with Cloudbees Jenkins Enterprise, running on Red Hat OpenShift. The Platform/SWT native fragment builds have moved to Eclipse CBI.
  • Bandwidth and performance: Our bandwidth cap was increased significantly, from 250 Mbps to 350 Mbps, in 2016. In 2017, a new transparent mirroring system was put in place to allow retrieving files from local mirrors even when a request is made to the Eclipse download servers directly. With this change, we’ve reduced our bandwidth cap back to 250 Mbps, thus reducing costs.
  • Developers, Developers, Developers: Eclipse’s account database now sits at 380,000 accounts, with an average growth rate of approximately 5000 new accounts each month (up from an average of 3000/mo in 2017).

Back to the top