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