blob: 55dff1efece23dc87c6e0b3f7af6099ccd5a456a [file] [log] [blame]
Stephan Herrmanncd0f7072011-06-13 16:43:35 +00001###############################################################################
2# feature.properties
3# contains externalized strings for feature.xml
4# "%foo" in feature.xml corresponds to the key "foo" in this file
5# java.io.Properties file (ISO 8859-1 with "\" escapes)
6# This file should be translated.
7
8featureName=Maven Integration for Object Teams (Early Access)
9providerName=Eclipse.org - Object Teams
10
11# "licenseURL" property - URL of the "Feature License"
12# do not translate value - just change to point to a locale-specific HTML page
13licenseURL=license.html
14
15# "license" property - text of the "Feature Update License"
16# should be plain text version of license agreement pointed to be "licenseURL"
17license=\
18Eclipse Foundation Software User Agreement\n\
Stephan Herrmann5c795f62014-05-27 19:19:33 +020019April 9, 2014\n\
Stephan Herrmanncd0f7072011-06-13 16:43:35 +000020\n\
21Usage Of Content\n\
22\n\
23THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR\n\
24OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
25USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
26AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
27NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU\n\
28AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
29AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
30OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE\n\
31TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
32OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
33BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
34\n\
35Applicable Licenses\n\
36\n\
37Unless otherwise indicated, all Content made available by the\n\
38Eclipse Foundation is provided to you under the terms and conditions of\n\
39the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is\n\
40provided with this Content and is also available at http://www.eclipse.org/legal/epl-v10.html.\n\
41For purposes of the EPL, "Program" will mean the Content.\n\
42\n\
43Content includes, but is not limited to, source code, object code,\n\
44documentation and other files maintained in the Eclipse Foundation source code\n\
45repository ("Repository") in software modules ("Modules") and made available\n\
46as downloadable archives ("Downloads").\n\
47\n\
Stephan Herrmann5c795f62014-05-27 19:19:33 +020048\t- Content may be structured and packaged into modules to facilitate delivering,\n\
49\t extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"),\n\
50\t plug-in fragments ("Fragments"), and features ("Features").\n\
51\t- Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java(TM) ARchive)\n\
52\t in a directory named "plugins".\n\
53\t- A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.\n\
54\t Each Feature may be packaged as a sub-directory in a directory named "features".\n\
55\t Within a Feature, files named "feature.xml" may contain a list of the names and version\n\
56\t numbers of the Plug-ins and/or Fragments associated with that Feature.\n\
57\t- Features may also include other Features ("Included Features"). Within a Feature, files\n\
58\t named "feature.xml" may contain a list of the names and version numbers of Included Features.\n\
Stephan Herrmanncd0f7072011-06-13 16:43:35 +000059\n\
60The terms and conditions governing Plug-ins and Fragments should be\n\
61contained in files named "about.html" ("Abouts"). The terms and\n\
62conditions governing Features and Included Features should be contained\n\
63in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
64Licenses may be located in any directory of a Download or Module\n\
65including, but not limited to the following locations:\n\
66\n\
Stephan Herrmann5c795f62014-05-27 19:19:33 +020067\t- The top-level (root) directory\n\
68\t- Plug-in and Fragment directories\n\
69\t- Inside Plug-ins and Fragments packaged as JARs\n\
70\t- Sub-directories of the directory named "src" of certain Plug-ins\n\
71\t- Feature directories\n\
Stephan Herrmanncd0f7072011-06-13 16:43:35 +000072\n\
73Note: if a Feature made available by the Eclipse Foundation is installed using the\n\
74Provisioning Technology (as defined below), you must agree to a license ("Feature \n\
75Update License") during the installation process. If the Feature contains\n\
76Included Features, the Feature Update License should either provide you\n\
77with the terms and conditions governing the Included Features or inform\n\
78you where you can locate them. Feature Update Licenses may be found in\n\
79the "license" property of files named "feature.properties" found within a Feature.\n\
80Such Abouts, Feature Licenses, and Feature Update Licenses contain the\n\
81terms and conditions (or references to such terms and conditions) that\n\
82govern your use of the associated Content in that directory.\n\
83\n\
84THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER\n\
85TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.\n\
86SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n\
87\n\
Stephan Herrmann5c795f62014-05-27 19:19:33 +020088\t- Eclipse Distribution License Version 1.0 (available at http://www.eclipse.org/licenses/edl-v1.0.html)\n\
89\t- Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)\n\
90\t- Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)\n\
91\t- Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)\n\
92\t- Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)\n\
Stephan Herrmanncd0f7072011-06-13 16:43:35 +000093\n\
94IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR\n\
95TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License\n\
96is provided, please contact the Eclipse Foundation to determine what terms and conditions\n\
97govern that particular Content.\n\
98\n\
99\n\Use of Provisioning Technology\n\
100\n\
101The Eclipse Foundation makes available provisioning software, examples of which include,\n\
102but are not limited to, p2 and the Eclipse Update Manager ("Provisioning Technology") for\n\
103the purpose of allowing users to install software, documentation, information and/or\n\
104other materials (collectively "Installable Software"). This capability is provided with\n\
105the intent of allowing such users to install, extend and update Eclipse-based products.\n\
106Information about packaging Installable Software is available at\n\
107http://eclipse.org/equinox/p2/repository_packaging.html ("Specification").\n\
108\n\
109You may use Provisioning Technology to allow other parties to install Installable Software.\n\
110You shall be responsible for enabling the applicable license agreements relating to the\n\
111Installable Software to be presented to, and accepted by, the users of the Provisioning Technology\n\
112in accordance with the Specification. By using Provisioning Technology in such a manner and\n\
113making it available in accordance with the Specification, you further acknowledge your\n\
114agreement to, and the acquisition of all necessary rights to permit the following:\n\
115\n\
Stephan Herrmann5c795f62014-05-27 19:19:33 +0200116\t1. A series of actions may occur ("Provisioning Process") in which a user may execute\n\
117\t the Provisioning Technology on a machine ("Target Machine") with the intent of installing,\n\
118\t extending or updating the functionality of an Eclipse-based product.\n\
119\t2. During the Provisioning Process, the Provisioning Technology may cause third party\n\
120\t Installable Software or a portion thereof to be accessed and copied to the Target Machine.\n\
121\t3. Pursuant to the Specification, you will provide to the user the terms and conditions that\n\
122\t govern the use of the Installable Software ("Installable Software Agreement") and such\n\
123\t Installable Software Agreement shall be accessed from the Target Machine in accordance\n\
124\t with the Specification. Such Installable Software Agreement must inform the user of the\n\
125\t terms and conditions that govern the Installable Software and must solicit acceptance by\n\
126\t the end user in the manner prescribed in such Installable Software Agreement. Upon such\n\
127\t indication of agreement by the user, the provisioning Technology will complete installation\n\
128\t of the Installable Software.\n\
Stephan Herrmanncd0f7072011-06-13 16:43:35 +0000129\n\
130Cryptography\n\
131\n\
132Content may contain encryption software. The country in which you are\n\
133currently may have restrictions on the import, possession, and use,\n\
134and/or re-export to another country, of encryption software. BEFORE\n\
135using any encryption software, please check the country's laws,\n\
136regulations and policies concerning the import, possession, or use, and\n\
137re-export of encryption software, to see if this is permitted.\n\
138\n\
139Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.\n
140########### end of license property ##########################################