| Summary: | Participating to Kepler | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Dennis Huebner <dennis.huebner> |
| Component: | Releng | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | Ed.Merks, mknauer |
| Version: | 2.0 | ||
| Target Milestone: | 2.0 M2 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Dennis Huebner
This time it is a bit more work than just reactivating our old Juno contribution, since we are going to contribute the first RAP 2.0 milestone to Kepler M1 in about one week. Please have a look into our migration guide, because on our way to RAP 2.0 we are doing a lot of refactorings, and renamed quite a few things: http://eclipse.org/rap/noteworthy/2.0/migration-guide/ In addition to that many RAP bundles are being upgraded to version 2.0.0. The p2 repository with the RAP 2.0 nightly build can be found here... it's worth to try that as soon as possible: http://download.eclipse.org/rt/rap/nightly/runtime/ If you find any problems or if there are any questions, please let us know... :-) Thanks for fast response and important information about Rap 2.0. I will fill a migration bug against EMF. Just for our book keeping and reference: What's the number of the EMF-migration bug? Maybe you've noticed that I tried to contribute a RAP-2.0-pre-M1-testbuild to the Kepler Simultaneous Release Repository in the meantime. I 'tried' this because the build is broken at the moment, but I hope this will help you to verify your changes in EMF. https://bugs.eclipse.org/bugs/show_bug.cgi?id=387180 I deactivated the EMF RAP feature contribution in our aggregation model. As long as we can migrate our code and set up the build, EMF Rap feature will be not contributed. Closing as RESOLVED. Since Kepler M2 all RAP Runtime and RAP Tools features are available from the common Kepler repository at /releases/staging. |