Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335766 - Use shared license in features
Summary: Use shared license in features
Status: RESOLVED WORKSFORME
Alias: None
Product: RAP
Classification: RT
Component: Releng (show other bugs)
Version: 1.4   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-29 09:50 EST by Ralf Sternberg CLA
Modified: 2013-06-04 05:10 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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