Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
former_member185231
Active Participant
0 Kudos

End of support for Eclipse Kepler in SAP HANA Cloud Platform Tools planned for end of July 2015

As you know, currently the Eclipse Tools for SAP HANA Cloud Platform support Kepler and Luna release trains of the Eclipse platform. Kepler is the release from June 2013 and its end of maintenance was in February 2014, Luna is the release from June 2014 with end of maintenance in February 2015, Mars is the current release under development which will be released in June 2015.

We would like to stop the support for Kepler in the end of July 2015, when Mars will be released. This is more than one year after the end of support by Eclipse.org. We will reallocate the resources that will become free for the early adoption of Mars – to ensure that it will be released in July 2015 with the desired quality for SAP HANA Cloud Platform.

Eclipse TrainReleased by Eclipse.orgEnd of Maintenance by Eclipse.orgPlanned End of Support by SAP HANA Cloud Platform
KeplerJune 2013February 2014June 2015
LunaJune 2014February 2015June 2016
MarsJune 2015February 2016June 2017

What does “end of support for Kepler” exactly mean? We will stop delivering new versions (both features and fixes) of the Eclipse Tools for SAP HANA Cloud Platform on the Kepler update site (https://tools.hana.ondemand.com/kepler). However, the update site will remain available as long as the last version of the tools for Kepler continue working with the SAP HANA Cloud Platform. When the cloud platform changes in a way that the Kepler version of the tools does not work anymore, we will shut down this branch of the update site.

I encourage everybody who is still using Eclipse Kepler to upgrade to Eclipse Luna.

If anyone sees any problem with this plan, please speak up by posting a comment in this discussion.

4 Comments