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

Bug 354707

Summary: [Releng] Split runtime repository into RAP and third-party additions
Product: [RT] RAP Reporter: Ralf Sternberg <rsternberg>
Component: RelengAssignee: Project Inbox <rap-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3    
Version: 1.5   
Target Milestone: 1.5 M1   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Ralf Sternberg CLA 2011-08-14 15:06:53 EDT
Currently the runtime includes both the RAP bundles and those bundles that are required for a basic RAP target platform. The latter are copies of bundles produced by other Eclipse projects. Having both kinds of artifacts together in one feature makes the target hard to build and to consume.

At build time, this would allow us to build, sign, and pack200 only our own bundles. We would, for example, not have to exclude certain third-party bundles from signing as we do now.

For those who assemble their own target it would be helpful to include only the RAP bundles and combine them with other target features such as the Equinox Core SDK.

I'd therefore suggest to split the runtime into two features: one for the RAP artifacts itself, and one for third party additions that are needed to create a basic RAP target.
Comment 1 Ralf Sternberg CLA 2011-08-22 05:55:59 EDT
As of RAP 1.5M1, we have two features:
org.eclipse.rap.runtime
  contains only RAP bundles
org.eclipse.rap.runtime.requirements
  contains everything that is needed for a basic RAP target.