|Re: Accept licenses and terms for all the Eclipse plugins (900+)? [message #1689006 is a reply to message #1688371]
||Sun, 22 March 2015 11:30
|| Eike Stepper
Registered: July 2009
Am 20.03.2015 um 16:07 schrieb M Jääskeläinen:|
> I have downloaded Eclipse for RCP and RAP Developers.
> It comes with many features and plugins. Additionally I have downloaded some other needed plugins from Eclipse
> I'd like to ask about Eclipse Foundation Software User Agreement that states by downloading Eclipse, I need to read
> and accept the terms and licenses in all the plugins. "IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND
> CONDITIONS PRIOR TO USE OF THE CONTENT"
> I have currently over 900 plugins in my Eclipse. How can I actually read over 900 about.html files for licenses?
I assume that you are referring to "Third Party Content" as described in http://eclipse.org/legal/epl/about.php . I've
also wondered how that's supposed to be handled by users. I could not find evidence that p2 "knows" about this extra
legal content (at least not in the metadata) and, hence, does NOT even present it at (before) install time. So I guess
you'll have to install what you want to install and, once you've restarted, find all plugins, and search for all
about.html files in them (in all their folders!), and then uninstall the plugins with unacceptable content.
I agree that this procedure sounds itself unacceptable, so there may be a better way that we just don't know about. I've
cc'ed Janet in the hope that she can shed light on this.
BTW., a good example is the org.apache.ant plugin in Orbit. Its about.html mentions other licenses at apache.org,
w3.org, and saxproject.org. But p2's metadata for that plugin knows nothing about those:
<unit id='org.apache.ant' version='1.9.4.v201410062020' singleton='false'>
<update id='org.apache.ant' range='[0.0.0,1.9.4.v201410062020)' severity='0'/>
<property name='df_LT.providerName' value='Eclipse Orbit'/>
<property name='df_LT.pluginName' value='Apache Ant'/>
<property name='org.eclipse.equinox.p2.name' value='%pluginName'/>
<property name='org.eclipse.equinox.p2.provider' value='%providerName'/>
<property name='org.eclipse.equinox.p2.bundle.localization' value='plugin'/>
<artifact classifier='osgi.bundle' id='org.apache.ant' version='1.9.4.v201410062020'/>
<touchpoint id='org.eclipse.equinox.p2.osgi' version='1.0.0'/>
> How all this licensing should be handled actually, because Eclipse is so modular and relies on 3rd party plugins also?
Powered by FUDForum
. Page generated in 0.04013 seconds