Your software was designed and implemented to run on a specific version of the Eclipse runtimes, but after a year that release is no longer actively supported by the Eclipse community. Migrating to the latest supported version of Eclipse can be time consuming, costly or even risky, depending on your application.

Eclipse Maintenance from EclipseSource offers dependable ongoing support for the platform you are using, and makes it possible to remain on an older version of Eclipse while continuing to maintain your software.

Eclipse Maintenance Features

• We provide support, including patches and minor enhancements, for the three most recent Eclipse releases. At the time of writing, this includes Helios (Eclipse 3.6) Galileo (Eclipse 3.5) and Ganymede (Eclipse 3.4).
• Customers receive a subscription to the EclipseSource maintenance repository for their specific release and can also commission patches or enhancements they require.
• Eclipse Maintenance includes coverage for the key runtime technologies as well as other projects.  You can purchase maintenance for the full stack - including RCP, Equinox, RAP, ECF, p2, Zest and g-Eclipse - or for individual projects.

Eclipse Maintenance gives you control of migration path by allowing you to remain supported on your current version of Eclipse long after community support for that release has expired.

Extending Support for Your Customers

If your customers are using software that you developed based on an Eclipse platform, they are even more likely to require deployment on versions of Eclipse that are no longer supported. Eclipse Maintenance can help you address the support and maintenance requirements of these customers.

Preserving the Path Forward

Just because you are using an older version of Eclipse now doesn’t mean you won't eventually want to migrate. You need to ensure that the changes you make to your current Eclipse release won't cut off migration paths for the future. Because EclipseSource team members are directly involved in ongoing Eclipse development, we can provide informed maintenance decisions to ensure that your future migration path remains open. We will help to manage the delta between how your code interacts with legacy Eclipse releases and how it will need to interact with future versions.