Community
Participate
Working Groups
Add the Eclipse Distribution License[1] to list of "other" licenses in the "Applicable Licenses" section of the Eclipse Foundation Software User Agreement[2]. The plain HTML[3] and Java Properties[4] versions of the SUA will also have to be updated as well. [1] http://www.eclipse.org/org/documents/edl-v10.php [2] http://www.eclipse.org/legal/epl/notice.php [3] http://www.eclipse.org/legal/epl/notice.html [4] http://www.eclipse.org/legal/epl/feature.properties.txt
I should add that this change will happen *after* Helios ships.
There is also this copy which still refers to the March 2005 edition of the SUA: http://eclipse.org/licenses/notice.html
John, I believe that copy of the SUA has been left on the server strictly as an archive. Do you know of anywhere it is actually linked to or used?
Ping ... any progress here ?
(In reply to comment #4) > Ping ... > > any progress here ? Matthias, My apologies. I did not realize that there was a time constraint other than Indigo. It will be done soon.
To cross reference, see also bug 278078. (Not sure, but maybe one could be "dup'ed" to other ... seem the same to my quick reading).
All projects need to make changes to their features when the SUA changes, so please try to make this available as soon as possible if you want to see it adopted for the Indigo release. I suggest M6 as a reasonable cut-off, beyond which it might be difficult to get every project to switch in time (March 18).
(In reply to comment #7) > All projects need to make changes to their features when the SUA changes, so > please try to make this available as soon as possible if you want to see it > adopted for the Indigo release. I suggest M6 as a reasonable cut-off, beyond > which it might be difficult to get every project to switch in time (March 18). The changes have been completed. I updated the following files: /legal/epl/notice.php /legal/epl/notice.html /legal/epl/feature.properties.txt If you could please doublecheck to make sure there are no trailing spaces, etc. it would be appreciated.
They look good wrt whitespace. Shouldn't the date change from April 2010 -> Feb 2011 to indicate there is a difference?
(In reply to comment #9) > They look good wrt whitespace. Shouldn't the date change from April 2010 -> Feb > 2011 to indicate there is a difference? Duh. Thanks. Done.
Should this be resolved as fixed or are there more changes coming and projects should not update yet?
(In reply to comment #11) > Should this be resolved as fixed or are there more changes coming and projects > should not update yet? There are no other changes that I am aware of, so I'm doing as you suggested. Go ahead and use what's there.
Just want to clarify that this change is required for Indigo, not Helios SR2?
(In reply to comment #13) > Just want to clarify that this change is required for Indigo, not Helios SR2? Correct, Just Indigo, not maintenance.
I just wanted to make sure that I've got this right from the project maintenance side. 1. Replace all instances of license= property in feature.properties with /legal/epl/feature.properties.txt 2. Replace all license.html files with contents of /legal/epl/notice.html ?
(In reply to comment #15) > I just wanted to make sure that I've got this right from the project > maintenance side. > > 1. Replace all instances of license= property in feature.properties with > /legal/epl/feature.properties.txt > > 2. Replace all license.html files with contents of /legal/epl/notice.html > > ? Yes, that is correct. There are some other approaches, though. It would be just about as much work first time through ... but, in the future, the theory goes, you'd have to changed just about nothing in your features or build the next time the license file changes ... you we all know, its not a question of "if", just "when" :) The best source of information about this other option is Kim Moir's excellent blog post at http://relengofthenerds.blogspot.com/2011/01/implementing-shared-licenses-with-37m5.html The basic idea of this new approach is that, once set up correct, it pulls in the license text and files at build time, so you only need to change the license source (or, pointer to the source, to be exact) to get everything updated automatically. Much easier next time around. But, to do the new approach, you do need to make about 5 changes to your feature files to get things setup, so this first time change would not be much easier that your original suggestion ... if doing it all "by hand". But there is a tool that helps you make those 5 or so changes to your features automatically, in one quick run against features loaded in your workspace. The releng tool is documented at http://wiki.eclipse.org/WTP/Releng/Tools. Also, you might want read bug 337934 where these approaches and issues have been discussed by others.
