blob: 8c250e2747bfcb9326644a6071e9a8db3bd1f43b [file] [log] [blame]
david_williamsc293a512006-02-05 06:41:15 +00001###############################################################################
2# Copyright (c) 2000, 2005 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###############################################################################
11# feature.properties
12# contains externalized strings for feature.xml
13# "%foo" in feature.xml corresponds to the key "foo" in this file
14# java.io.Properties file (ISO 8859-1 with "\" escapes)
15# This file should be translated.
16
17# "featureName" property - name of the feature
david_williams6b9bc372006-02-15 02:05:49 +000018featureName=XML UI feature plugins
david_williamsc293a512006-02-05 06:41:15 +000019
20# "providerName" property - name of the company that provides the feature
21providerName=Eclipse.org
22
23# "updateSiteName" property - label for the update site
david_williams6b9bc372006-02-15 02:05:49 +000024updateSiteName=Web Tools Platform (WTP) Updates
david_williamsc293a512006-02-05 06:41:15 +000025
26# "description" property - description of the feature
27description=API documentation and source code zips for Eclipse Java development tools.
28
29# "licenseURL" property - URL of the "Feature License"
30# do not translate value - just change to point to a locale-specific HTML page
31licenseURL=license.html
32
33# "license" property - text of the "Feature Update License"
34# should be plain text version of license agreement pointed to be "licenseURL"
35license=\
36ECLIPSE FOUNDATION SOFTWARE USER AGREEMENT\n\
37March 17, 2005\n\
38\n\
39Usage Of Content\n\
40\n\
41THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR\n\
42OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
43USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
44AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
45NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU\n\
46AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
47AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
48OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE\n\
49TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
50OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
51BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
52\n\
53Applicable Licenses\n\
54\n\
55Unless otherwise indicated, all Content made available by the Eclipse Foundation\n\
56is provided to you under the terms and conditions of the Eclipse Public\n\
57License Version 1.0 ("EPL"). A copy of the EPL is provided with this\n\
58Content and is also available at http://www.eclipse.org/legal/epl-v10.html.\n\
59For purposes of the EPL, "Program" will mean the Content.\n\
60\n\
61Content includes, but is not limited to, source code, object code,\n\
62documentation and other files maintained in the Eclipse.org CVS\n\
63repository ("Repository") in CVS modules ("Modules") and made available\n\
64as downloadable archives ("Downloads").\n\
65\n\
66 - Content may be structured and packaged into modules to facilitate delivering,\n\
67 extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"),\n\
68 plug-in fragments ("Fragments"), and features ("Features").\n\
69 - Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java? ARchive)\n\
70 in a directory named "plugins".\n\
71 - A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.\n\
72 Each Feature may be packaged as a sub-directory in a directory named "features".\n\
73 Within a Feature, files named "feature.xml" may contain a list of the names and version\n\
74 numbers of the Plug-ins and/or Fragments associated with that Feature.\n\
75 - Features may also include other Features ("Included Features"). Within a Feature, files\n\
76 named "feature.xml" may contain a list of the names and version numbers of Included Features.\n\
77\n\
78Features may also include other Features ("Included Features"). Files named\n\
79"feature.xml" may contain a list of the names and version numbers of\n\
80Included Features.\n\
81\n\
82The terms and conditions governing Plug-ins and Fragments should be\n\
83contained in files named "about.html" ("Abouts"). The terms and\n\
84conditions governing Features and Included Features should be contained\n\
85in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
86Licenses may be located in any directory of a Download or Module\n\
87including, but not limited to the following locations:\n\
88\n\
89 - The top-level (root) directory\n\
90 - Plug-in and Fragment directories\n\
91 - Inside Plug-ins and Fragments packaged as JARs\n\
92 - Sub-directories of the directory named "src" of certain Plug-ins\n\
93 - Feature directories\n\
94\n\
95Note: if a Feature made available by the Eclipse Foundation is installed using the\n\
96Eclipse Update Manager, you must agree to a license ("Feature Update\n\
97License") during the installation process. If the Feature contains\n\
98Included Features, the Feature Update License should either provide you\n\
99with the terms and conditions governing the Included Features or inform\n\
100you where you can locate them. Feature Update Licenses may be found in\n\
101the "license" property of files named "feature.properties". Such Abouts,\n\
102Feature Licenses and Feature Update Licenses contain the terms and\n\
103conditions (or references to such terms and conditions) that govern your\n\
104use of the associated Content in that directory.\n\
105\n\
106THE ABOUTS, FEATURE LICENSES AND FEATURE UPDATE LICENSES MAY REFER\n\
107TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.\n\
108SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n\
109\n\
110 - Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)\n\
111 - Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)\n\
112 - Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)\n\
113 - IBM Public License 1.0 (available at http://oss.software.ibm.com/developerworks/opensource/license10.html)\n\
114 - Metro Link Public License 1.00 (available at http://www.opengroup.org/openmotif/supporters/metrolink/license.html)\n\
115 - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)\n\
116\n\
117IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR\n\
118TO USE OF THE CONTENT. If no About, Feature License or Feature Update License\n\
119is provided, please contact the Eclipse Foundation to determine what terms and conditions\n\
120govern that particular Content.\n\
121\n\
122Cryptography\n\
123\n\
124Content may contain encryption software. The country in which you are\n\
125currently may have restrictions on the import, possession, and use,\n\
126and/or re-export to another country, of encryption software. BEFORE\n\
127using any encryption software, please check the country's laws,\n\
128regulations and policies concerning the import, possession, or use,\n\
129and re-export of encryption software, to see if this is permitted.\n\
130\n\
131Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.\n
132########### end of license property ##########################################