Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 517940

Summary:	[e4] Move RAP E4 components from incubator to main RAP Runtime project
Product:	[RT] RAP	Reporter:	Markus Knauer <mknauer>
Component:	Releng	Assignee:	Markus Knauer <mknauer>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	ivan, mknauer, tom.schindl
Version:	3.2
Target Milestone:	3.2
Hardware:	All
OS:	All
See Also:	https://git.eclipse.org/r/#/c/97150/ https://git.eclipse.org/r/#/c/97151/ https://git.eclipse.org/r/#/c/97152/ https://git.eclipse.org/r/#/c/97154/ https://git.eclipse.org/r/#/c/98691/ https://git.eclipse.org/r/#/c/98723/
Whiteboard:

Description Markus Knauer

2017-06-07 08:37:16 EDT

After existing for some years in the RAP Incubator (and after going through multiple rounds of fixing memory leaks in customer real-life projects) we believe that it is long overdue for the runtime parts of the RAP E4 Incubator project to be moved to the RAP Runtime project.

In particular, this is about moving the following projects from http://git.eclipse.org/c/rap/incubator/org.eclipse.rap.incubator.e4.git to the RAP Runtime project:

- bundles/org.eclipse.e4.core.commands
- bundles/org.eclipse.e4.ui.bindings
- bundles/org.eclipse.e4.ui.workbench
- bundles/org.eclipse.e4.ui.workbench.addons.swt
- bundles/org.eclipse.e4.ui.workbench.renderers.swt
- bundles/org.eclipse.e4.ui.workbench.swt
- bundles/org.eclipse.rap.e4
- examples/org.eclipse.rap.e4.demo
- features/org.eclipse.rap.e4.base.feature
- features/org.eclipse.rap.e4.target.feature

These projects are to be integrated into the main RAP Runtime build. After their migration they will be removed from the RAP Incubator.

RAP artifacts will get incremented version numbers to align them with the RAP release. Other artifacts, in particular those that have been forked for the RAP E4 project, will stay on their old level.

For the time being there are no plans to move the "tools" part of the RAP E4 Incubator, i.e. they will stay there.

The build output will be put in a p2 repository separate from the other RAP Runtime p2 repository in order to keep these bits separate from other projects' contributions, and to give consumers the chance to explicitly decide about which parts to consume. The new p2 repository will be one path segment below the RAP Runtime repository, e.g. '.../rap/3.2/e4'.

None of those new artifacts will be contributed to the (Oxygen) Simultaneous Release. While we took multiple measures to handle the forked bundles in a careful way (via p2 metadata, via OSGi mechanisms, via dedicated version qualifiers), we are sure that there could be unwanted side-effects. For the foreseeable future and until we learn enough about to mitigate those side-effects, there are no plans to change this.