RAP 2.1 Released

rap logo 21 RAP 2.1 Released

As every year in June, the RAP project has released a brand new version together with the annual Eclipse release. Last year, we shipped RAP 1.5 with Eclipse Juno, this time we’re already onto Release 2.1. A lot has been going on in the meantime.

In February we released RAP 2.0–the first release that builds entirely on the open JSON protocol and supports alternative RAP clients. With this release, we’ve revised our APIs and also changed our name to “Remote Application Platform”. This was done between the big Eclipse releases to help give early adopters a chance to try out the new concepts and APIs.

RAP 2.1 is a follow-up release that contains lots of improvements and also adds a bunch of new features. For example, extended support for key shortcuts including mnemonics, out-of-the-box multi-tab support, support for selection listeners on hyperlinks in markup, and drawing paths including quadratic and Bézier curves. For a full list of features, please check out our New and Noteworthy. If you’re upgrading directly from last year’s version, you should also check out RAP 2.0 New and Noteworthy and the Migration Guide.

I’ve already heard from a number of projects that the migration has gone smoothly. So, there’s really no excuse to stay with any older RAP versions. icon wink RAP 2.1 Released However, if you have to stay with 2.0 for whatever reason, please upgrade to the 2.0.1 service release which fixes a critical bug.

RAP 2.1 is now available for download. If you download the Kepler package for RAP and RCP developers, the 2.1 RAP tools are already included.

Thanks to everyone who helped with this release by contributing ideas, reporting bugs, and discussing in the RAP forum!

You may also like...

Share this Post

Twitter10
Google+1
LinkedIn
Facebook

Tags

8 Responses to “RAP 2.1 Released”

  1. minda says:

    The project “incubator/org.eclipse.rap.incubator.gef” is suited for 2.1 ? or The project “incubator/org.eclipse.rap.incubator.gef” is dead?

  2. Ralf Sternberg says:

    Let’s not call it dead, but yes, it’s maintainer didn’t find the time to update it. As far as I know, this incubator component is looking for a new maintainer.

  3. D2002 says:

    I migrated from 1.5 to 2.0 and more recently to 2.1 RC.
    My server is a Raspberry (512MB) loaded with Oracle JVM and tomcat 6/7.
    I shall say that 2.0 brought a real improvement (about 25 to 33%) in term of performances.
    For me RAP is a real opportunity to distribute application on low cost ARM box in a convenient way that does not require knowledge for the final user.

    All my thanks to the RAP project for their accomplishment.

  4. Ralf Sternberg says:

    I’m so happy to hear this, thanks!

  5. Philippe says:

    Hi there, i try to generate a RAP 2.1 App with the “bowling” EMF-Model supplied by
    Maximilian Koegel (Emf Tutorial). I’m not sure if i’m doing something wrong but since i installed RAP 2.1 as a Target Platform i should be able to generate all needed Plugins (Edit, Editor, Test) for Runtime Plattform “RAP” and run the Modeler Plugin as RAP Application, right? Is 2.1 supporting for EMF?

  6. Hi Philippe,

    unfortunately the EMF Editor does not run on RAP without modifications to my best knowledge. Maybe you want to give EMF Client Platform a try, it supports RAP. Let me know if you want to do this, I can send you detailed instructions (mkoegel@eclipsesource.com).

    Best regards,
    Maximilian

  7. Hi Philippe,

    an update, the editor works fine with RAP 2.1 following this tutorial:
    http://wiki.eclipse.org/EMF_Editor_goes_RAP
    With three minor modifications:
    - org.eclipse.emf.edit has to be added to the dependencies of the editor
    - org.eclipse.rap.ui has to be added to the dependencies of the editor
    - you need to add an extension for org.eclipse.rap.ui.entrypoint. In the extension the applicationId is LibraryEditorAdvisorApplication
    I will open a Bug for EMF to fix this.

    Cheers,
    Maximilian

  8. Charles Tubbs says:

    I migrated from 1.5 to 2.0 on Juno a while back. After moving to Kepler and 2.1 I get a FrameworkEvent error complaining that org.eclipse.jdt.junit.runtime_3.4.400.v20130514-0733 could not be resolved due to a missing constraint: org.junit; bundle-version=”3.8.2″

    Is there something else I need to install to run 2.1 on Kepler?

8 responses so far

Written by . Published in Categories: EclipseSource News, Planet Eclipse

Author:
Published:
Jun 26th, 2013
Bookmark:
Follow:

Twitter Google+ GitHub