blob: dcfcff629f5c7f9080aa5ede7b4e2f814a876cbe [file] [log] [blame]
Stephan Herrmannf3a36a02010-04-01 21:25:08 +00001###############################################################################
2# Copyright (c) 2000, 2010 IBM Corporation and others.
3# All rights reserved. This program and the accompanying materials
4# are made available under the terms of the Eclipse Public License v1.0
5# which accompanies this distribution, and is available at
6# http://www.eclipse.org/legal/epl-v10.html
7#
8# Contributors:
9# IBM Corporation - initial API and implementation
10# Fraunhofer FIRST - initial API and implementation
11# Technical University Berlin - initial API and implementation
12###############################################################################
13# feature.properties
14# contains externalized strings for feature.xml
15# "%foo" in feature.xml corresponds to the key "foo" in this file
16# java.io.Properties file (ISO 8859-1 with "\" escapes)
17# This file should be translated.
18
Stephan Herrmann98502132010-04-02 14:34:38 +000019featureName=Object Teams Patch for JDT/Core (Incubation)
Stephan Herrmannbd831d92010-06-12 16:41:14 +000020providerName=Eclipse.org - Object Teams
Stephan Herrmann98502132010-04-02 14:34:38 +000021
Stephan Herrmannf3a36a02010-04-01 21:25:08 +000022# "licenseURL" property - URL of the "Feature License"
23# do not translate value - just change to point to a locale-specific HTML page
24licenseURL=license.html
25
26# "license" property - text of the "Feature Update License"
27# should be plain text version of license agreement pointed to be "licenseURL"
28license=\
Stephan Herrmann323637e2010-04-23 10:30:31 +000029Eclipse Foundation Software User Agreement\n\
Stephan Herrmannf45ca1c2011-02-28 18:44:37 +000030February 1, 2011\n\
Stephan Herrmannf3a36a02010-04-01 21:25:08 +000031\n\
32Usage Of Content\n\
33\n\
34THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR\n\
35OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
36USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
37AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
Stephan Herrmann323637e2010-04-23 10:30:31 +000038NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU\n\
Stephan Herrmannf3a36a02010-04-01 21:25:08 +000039AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
40AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
Stephan Herrmann323637e2010-04-23 10:30:31 +000041OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE\n\
Stephan Herrmannf3a36a02010-04-01 21:25:08 +000042TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
43OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
44BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
45\n\
46Applicable Licenses\n\
47\n\
Stephan Herrmann323637e2010-04-23 10:30:31 +000048Unless otherwise indicated, all Content made available by the\n\
49Eclipse Foundation is provided to you under the terms and conditions of\n\
50the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is\n\
51provided with this Content and is also available at http://www.eclipse.org/legal/epl-v10.html.\n\
Stephan Herrmannf3a36a02010-04-01 21:25:08 +000052For purposes of the EPL, "Program" will mean the Content.\n\
53\n\
54Content includes, but is not limited to, source code, object code,\n\
Stephan Herrmann323637e2010-04-23 10:30:31 +000055documentation and other files maintained in the Eclipse Foundation source code\n\
56repository ("Repository") in software modules ("Modules") and made available\n\
Stephan Herrmannf3a36a02010-04-01 21:25:08 +000057as downloadable archives ("Downloads").\n\
58\n\
Stephan Herrmann323637e2010-04-23 10:30:31 +000059 - Content may be structured and packaged into modules to facilitate delivering,\n\
60 extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"),\n\
61 plug-in fragments ("Fragments"), and features ("Features").\n\
62 - Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java(TM) ARchive)\n\
63 in a directory named "plugins".\n\
64 - A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.\n\
65 Each Feature may be packaged as a sub-directory in a directory named "features".\n\
66 Within a Feature, files named "feature.xml" may contain a list of the names and version\n\
67 numbers of the Plug-ins and/or Fragments associated with that Feature.\n\
68 - Features may also include other Features ("Included Features"). Within a Feature, files\n\
69 named "feature.xml" may contain a list of the names and version numbers of Included Features.\n\
Stephan Herrmannf3a36a02010-04-01 21:25:08 +000070\n\
71The terms and conditions governing Plug-ins and Fragments should be\n\
72contained in files named "about.html" ("Abouts"). The terms and\n\
73conditions governing Features and Included Features should be contained\n\
74in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
75Licenses may be located in any directory of a Download or Module\n\
76including, but not limited to the following locations:\n\
77\n\
Stephan Herrmann323637e2010-04-23 10:30:31 +000078 - The top-level (root) directory\n\
79 - Plug-in and Fragment directories\n\
80 - Inside Plug-ins and Fragments packaged as JARs\n\
81 - Sub-directories of the directory named "src" of certain Plug-ins\n\
82 - Feature directories\n\
Stephan Herrmannf3a36a02010-04-01 21:25:08 +000083\n\
84Note: if a Feature made available by the Eclipse Foundation is installed using the\n\
Stephan Herrmann323637e2010-04-23 10:30:31 +000085Provisioning Technology (as defined below), you must agree to a license ("Feature \n\
86Update License") during the installation process. If the Feature contains\n\
Stephan Herrmannf3a36a02010-04-01 21:25:08 +000087Included Features, the Feature Update License should either provide you\n\
88with the terms and conditions governing the Included Features or inform\n\
89you where you can locate them. Feature Update Licenses may be found in\n\
Stephan Herrmann323637e2010-04-23 10:30:31 +000090the "license" property of files named "feature.properties" found within a Feature.\n\
91Such Abouts, Feature Licenses, and Feature Update Licenses contain the\n\
92terms and conditions (or references to such terms and conditions) that\n\
93govern your use of the associated Content in that directory.\n\
Stephan Herrmannf3a36a02010-04-01 21:25:08 +000094\n\
Stephan Herrmann323637e2010-04-23 10:30:31 +000095THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER\n\
Stephan Herrmannf3a36a02010-04-01 21:25:08 +000096TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.\n\
97SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n\
98\n\
Stephan Herrmannf45ca1c2011-02-28 18:44:37 +000099 - Eclipse Distribution License Version 1.0 (available at http://www.eclipse.org/licenses/edl-v1.0.html)\n\
Stephan Herrmann323637e2010-04-23 10:30:31 +0000100 - Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)\n\
101 - Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)\n\
102 - Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)\n\
103 - Metro Link Public License 1.00 (available at http://www.opengroup.org/openmotif/supporters/metrolink/license.html)\n\
104 - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)\n\
Stephan Herrmannf3a36a02010-04-01 21:25:08 +0000105\n\
106IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR\n\
Stephan Herrmann323637e2010-04-23 10:30:31 +0000107TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License\n\
Stephan Herrmannf3a36a02010-04-01 21:25:08 +0000108is provided, please contact the Eclipse Foundation to determine what terms and conditions\n\
109govern that particular Content.\n\
110\n\
Stephan Herrmann323637e2010-04-23 10:30:31 +0000111\n\Use of Provisioning Technology\n\
112\n\
113The Eclipse Foundation makes available provisioning software, examples of which include,\n\
114but are not limited to, p2 and the Eclipse Update Manager ("Provisioning Technology") for\n\
115the purpose of allowing users to install software, documentation, information and/or\n\
116other materials (collectively "Installable Software"). This capability is provided with\n\
117the intent of allowing such users to install, extend and update Eclipse-based products.\n\
118Information about packaging Installable Software is available at\n\
119http://eclipse.org/equinox/p2/repository_packaging.html ("Specification").\n\
120\n\
121You may use Provisioning Technology to allow other parties to install Installable Software.\n\
122You shall be responsible for enabling the applicable license agreements relating to the\n\
123Installable Software to be presented to, and accepted by, the users of the Provisioning Technology\n\
124in accordance with the Specification. By using Provisioning Technology in such a manner and\n\
125making it available in accordance with the Specification, you further acknowledge your\n\
126agreement to, and the acquisition of all necessary rights to permit the following:\n\
127\n\
128 1. A series of actions may occur ("Provisioning Process") in which a user may execute\n\
129 the Provisioning Technology on a machine ("Target Machine") with the intent of installing,\n\
130 extending or updating the functionality of an Eclipse-based product.\n\
131 2. During the Provisioning Process, the Provisioning Technology may cause third party\n\
132 Installable Software or a portion thereof to be accessed and copied to the Target Machine.\n\
133 3. Pursuant to the Specification, you will provide to the user the terms and conditions that\n\
134 govern the use of the Installable Software ("Installable Software Agreement") and such\n\
135 Installable Software Agreement shall be accessed from the Target Machine in accordance\n\
136 with the Specification. Such Installable Software Agreement must inform the user of the\n\
137 terms and conditions that govern the Installable Software and must solicit acceptance by\n\
138 the end user in the manner prescribed in such Installable Software Agreement. Upon such\n\
139 indication of agreement by the user, the provisioning Technology will complete installation\n\
140 of the Installable Software.\n\
141\n\
Stephan Herrmannf3a36a02010-04-01 21:25:08 +0000142Cryptography\n\
143\n\
144Content may contain encryption software. The country in which you are\n\
145currently may have restrictions on the import, possession, and use,\n\
146and/or re-export to another country, of encryption software. BEFORE\n\
147using any encryption software, please check the country's laws,\n\
Stephan Herrmann323637e2010-04-23 10:30:31 +0000148regulations and policies concerning the import, possession, or use, and\n\
149re-export of encryption software, to see if this is permitted.\n\
Stephan Herrmannf3a36a02010-04-01 21:25:08 +0000150\n\
Stephan Herrmanna4b354d2010-04-25 11:51:21 +0000151Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.\n
152########### end of license property ##########################################