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

Bug 335766

Summary: Use shared license in features
Product: [RT] RAP Reporter: Ralf Sternberg <rsternberg>
Component: RelengAssignee: Project Inbox <rap-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: enhancement    
Priority: P3    
Version: 1.4   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Ralf Sternberg CLA 2011-01-29 09:50:26 EST 
Let's use a shared license as explained here:
http://relengofthenerds.blogspot.com/2011/01/implementing-shared-licenses-with-37m5.html
Comment 1 Ralf Sternberg CLA 2013-06-04 05:10:07 EDT 
This approach would allow us to keep the license text in a shared feature. However, it would require an additional feature (the "license feature"). Given the small number of features in RAP, I currently think that shared licenses would not really simplify matters for us. It's just another indirection.

Looking at the License Consistency report for Kepler [1], all our licenses are up to date.

[1] http://build.eclipse.org/simrel/kepler/reporeports/reports/licenseConsistency.html