1 <?xml version="1.0" encoding="ISO-8859-1" ?> |
|
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> |
|
3 <html xmlns="http://www.w3.org/1999/xhtml"> |
|
4 <head> |
|
5 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /> |
|
6 <title>Eclipse Foundation Software User Agreement</title> |
|
7 </head> |
|
8 |
|
9 <body lang="EN-US"> |
|
10 <h2>Eclipse Foundation Software User Agreement</h2> |
|
11 <p>April 14, 2010</p> |
|
12 |
|
13 <h3>Usage Of Content</h3> |
|
14 |
|
15 <p>THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS |
|
16 (COLLECTIVELY "CONTENT"). USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE TERMS AND |
|
17 CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE |
|
18 OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR |
|
19 NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND |
|
20 CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT USE THE CONTENT.</p> |
|
21 |
|
22 <h3>Applicable Licenses</h3> |
|
23 |
|
24 <p>Unless otherwise indicated, all Content made available by the Eclipse Foundation is provided to you under the terms and conditions of the Eclipse Public License Version 1.0 |
|
25 ("EPL"). A copy of the EPL is provided with this Content and is also available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>. |
|
26 For purposes of the EPL, "Program" will mean the Content.</p> |
|
27 |
|
28 <p>Content includes, but is not limited to, source code, object code, documentation and other files maintained in the Eclipse Foundation source code |
|
29 repository ("Repository") in software modules ("Modules") and made available as downloadable archives ("Downloads").</p> |
|
30 |
|
31 <ul> |
|
32 <li>Content may be structured and packaged into modules to facilitate delivering, extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"), plug-in fragments ("Fragments"), and features ("Features").</li> |
|
33 <li>Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java™ ARchive) in a directory named "plugins".</li> |
|
34 <li>A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material. Each Feature may be packaged as a sub-directory in a directory named "features". Within a Feature, files named "feature.xml" may contain a list of the names and version numbers of the Plug-ins |
|
35 and/or Fragments associated with that Feature.</li> |
|
36 <li>Features may also include other Features ("Included Features"). Within a Feature, files named "feature.xml" may contain a list of the names and version numbers of Included Features.</li> |
|
37 </ul> |
|
38 |
|
39 <p>The terms and conditions governing Plug-ins and Fragments should be contained in files named "about.html" ("Abouts"). The terms and conditions governing Features and |
|
40 Included Features should be contained in files named "license.html" ("Feature Licenses"). Abouts and Feature Licenses may be located in any directory of a Download or Module |
|
41 including, but not limited to the following locations:</p> |
|
42 |
|
43 <ul> |
|
44 <li>The top-level (root) directory</li> |
|
45 <li>Plug-in and Fragment directories</li> |
|
46 <li>Inside Plug-ins and Fragments packaged as JARs</li> |
|
47 <li>Sub-directories of the directory named "src" of certain Plug-ins</li> |
|
48 <li>Feature directories</li> |
|
49 </ul> |
|
50 |
|
51 <p>Note: if a Feature made available by the Eclipse Foundation is installed using the Provisioning Technology (as defined below), you must agree to a license ("Feature Update License") during the |
|
52 installation process. If the Feature contains Included Features, the Feature Update License should either provide you with the terms and conditions governing the Included Features or |
|
53 inform you where you can locate them. Feature Update Licenses may be found in the "license" property of files named "feature.properties" found within a Feature. |
|
54 Such Abouts, Feature Licenses, and Feature Update Licenses contain the terms and conditions (or references to such terms and conditions) that govern your use of the associated Content in |
|
55 that directory.</p> |
|
56 |
|
57 <p>THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE |
|
58 OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):</p> |
|
59 |
|
60 <ul> |
|
61 <li>Common Public License Version 1.0 (available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>)</li> |
|
62 <li>Apache Software License 1.1 (available at <a href="http://www.apache.org/licenses/LICENSE">http://www.apache.org/licenses/LICENSE</a>)</li> |
|
63 <li>Apache Software License 2.0 (available at <a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>)</li> |
|
64 <li>Metro Link Public License 1.00 (available at <a href="http://www.opengroup.org/openmotif/supporters/metrolink/license.html">http://www.opengroup.org/openmotif/supporters/metrolink/license.html</a>)</li> |
|
65 <li>Mozilla Public License Version 1.1 (available at <a href="http://www.mozilla.org/MPL/MPL-1.1.html">http://www.mozilla.org/MPL/MPL-1.1.html</a>)</li> |
|
66 </ul> |
|
67 |
|
68 <p>IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License is provided, please |
|
69 contact the Eclipse Foundation to determine what terms and conditions govern that particular Content.</p> |
|
70 |
|
71 |
|
72 <h3>Use of Provisioning Technology</h3> |
|
73 |
|
74 <p>The Eclipse Foundation makes available provisioning software, examples of which include, but are not limited to, p2 and the Eclipse |
|
75 Update Manager ("Provisioning Technology") for the purpose of allowing users to install software, documentation, information and/or |
|
76 other materials (collectively "Installable Software"). This capability is provided with the intent of allowing such users to |
|
77 install, extend and update Eclipse-based products. Information about packaging Installable Software is available at <a |
|
78 href="http://eclipse.org/equinox/p2/repository_packaging.html">http://eclipse.org/equinox/p2/repository_packaging.html</a> |
|
79 ("Specification").</p> |
|
80 |
|
81 <p>You may use Provisioning Technology to allow other parties to install Installable Software. You shall be responsible for enabling the |
|
82 applicable license agreements relating to the Installable Software to be presented to, and accepted by, the users of the Provisioning Technology |
|
83 in accordance with the Specification. By using Provisioning Technology in such a manner and making it available in accordance with the |
|
84 Specification, you further acknowledge your agreement to, and the acquisition of all necessary rights to permit the following:</p> |
|
85 |
|
86 <ol> |
|
87 <li>A series of actions may occur ("Provisioning Process") in which a user may execute the Provisioning Technology |
|
88 on a machine ("Target Machine") with the intent of installing, extending or updating the functionality of an Eclipse-based |
|
89 product.</li> |
|
90 <li>During the Provisioning Process, the Provisioning Technology may cause third party Installable Software or a portion thereof to be |
|
91 accessed and copied to the Target Machine.</li> |
|
92 <li>Pursuant to the Specification, you will provide to the user the terms and conditions that govern the use of the Installable |
|
93 Software ("Installable Software Agreement") and such Installable Software Agreement shall be accessed from the Target |
|
94 Machine in accordance with the Specification. Such Installable Software Agreement must inform the user of the terms and conditions that govern |
|
95 the Installable Software and must solicit acceptance by the end user in the manner prescribed in such Installable Software Agreement. Upon such |
|
96 indication of agreement by the user, the provisioning Technology will complete installation of the Installable Software.</li> |
|
97 </ol> |
|
98 |
|
99 <h3>Cryptography</h3> |
|
100 |
|
101 <p>Content may contain encryption software. The country in which you are currently may have restrictions on the import, possession, and use, and/or re-export to |
|
102 another country, of encryption software. BEFORE using any encryption software, please check the country's laws, regulations and policies concerning the import, |
|
103 possession, or use, and re-export of encryption software, to see if this is permitted.</p> |
|
104 |
|
105 <p><small>Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.</small></p> |
|
106 </body> |
|
107 </html> |
|