|
| 1 | +############################################################################### |
| 2 | +# Copyright (c) 2012, 2017 Inria 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 | +# Inria - 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 | +# NLS_MESSAGEFORMAT_VAR |
| 17 | + |
| 18 | + |
| 19 | +# "providerName" property - name of the company that provides the feature |
| 20 | +providerName=Eclipse Modeling Project |
| 21 | + |
| 22 | +# "licenseURL" property - URL of the "Feature License" |
| 23 | +# do not translate value - just change to point to a locale-specific HTML page |
| 24 | +licenseURL=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" |
| 28 | +license=\ |
| 29 | +Eclipse Foundation Software User Agreement\n\ |
| 30 | +April 9, 2014\n\ |
| 31 | +\n\ |
| 32 | +Usage Of Content\n\ |
| 33 | +\n\ |
| 34 | +THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR\n\ |
| 35 | +OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\ |
| 36 | +USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\ |
| 37 | +AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\ |
| 38 | +NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU\n\ |
| 39 | +AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\ |
| 40 | +AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\ |
| 41 | +OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE\n\ |
| 42 | +TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\ |
| 43 | +OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\ |
| 44 | +BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\ |
| 45 | +\n\ |
| 46 | +Applicable Licenses\n\ |
| 47 | +\n\ |
| 48 | +Unless otherwise indicated, all Content made available by the\n\ |
| 49 | +Eclipse Foundation is provided to you under the terms and conditions of\n\ |
| 50 | +the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is\n\ |
| 51 | +provided with this Content and is also available at http://www.eclipse.org/legal/epl-v10.html.\n\ |
| 52 | +For purposes of the EPL, "Program" will mean the Content.\n\ |
| 53 | +\n\ |
| 54 | +Content includes, but is not limited to, source code, object code,\n\ |
| 55 | +documentation and other files maintained in the Eclipse Foundation source code\n\ |
| 56 | +repository ("Repository") in software modules ("Modules") and made available\n\ |
| 57 | +as downloadable archives ("Downloads").\n\ |
| 58 | +\n\ |
| 59 | + - 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\ |
| 70 | +\n\ |
| 71 | +The terms and conditions governing Plug-ins and Fragments should be\n\ |
| 72 | +contained in files named "about.html" ("Abouts"). The terms and\n\ |
| 73 | +conditions governing Features and Included Features should be contained\n\ |
| 74 | +in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\ |
| 75 | +Licenses may be located in any directory of a Download or Module\n\ |
| 76 | +including, but not limited to the following locations:\n\ |
| 77 | +\n\ |
| 78 | + - 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\ |
| 83 | +\n\ |
| 84 | +Note: if a Feature made available by the Eclipse Foundation is installed using the\n\ |
| 85 | +Provisioning Technology (as defined below), you must agree to a license ("Feature \n\ |
| 86 | +Update License") during the installation process. If the Feature contains\n\ |
| 87 | +Included Features, the Feature Update License should either provide you\n\ |
| 88 | +with the terms and conditions governing the Included Features or inform\n\ |
| 89 | +you where you can locate them. Feature Update Licenses may be found in\n\ |
| 90 | +the "license" property of files named "feature.properties" found within a Feature.\n\ |
| 91 | +Such Abouts, Feature Licenses, and Feature Update Licenses contain the\n\ |
| 92 | +terms and conditions (or references to such terms and conditions) that\n\ |
| 93 | +govern your use of the associated Content in that directory.\n\ |
| 94 | +\n\ |
| 95 | +THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER\n\ |
| 96 | +TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.\n\ |
| 97 | +SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n\ |
| 98 | +\n\ |
| 99 | + - Eclipse Distribution License Version 1.0 (available at http://www.eclipse.org/licenses/edl-v1.0.html)\n\ |
| 100 | + - 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 | + - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)\n\ |
| 104 | +\n\ |
| 105 | +IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR\n\ |
| 106 | +TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License\n\ |
| 107 | +is provided, please contact the Eclipse Foundation to determine what terms and conditions\n\ |
| 108 | +govern that particular Content.\n\ |
| 109 | +\n\ |
| 110 | +\n\Use of Provisioning Technology\n\ |
| 111 | +\n\ |
| 112 | +The Eclipse Foundation makes available provisioning software, examples of which include,\n\ |
| 113 | +but are not limited to, p2 and the Eclipse Update Manager ("Provisioning Technology") for\n\ |
| 114 | +the purpose of allowing users to install software, documentation, information and/or\n\ |
| 115 | +other materials (collectively "Installable Software"). This capability is provided with\n\ |
| 116 | +the intent of allowing such users to install, extend and update Eclipse-based products.\n\ |
| 117 | +Information about packaging Installable Software is available at\n\ |
| 118 | +http://eclipse.org/equinox/p2/repository_packaging.html ("Specification").\n\ |
| 119 | +\n\ |
| 120 | +You may use Provisioning Technology to allow other parties to install Installable Software.\n\ |
| 121 | +You shall be responsible for enabling the applicable license agreements relating to the\n\ |
| 122 | +Installable Software to be presented to, and accepted by, the users of the Provisioning Technology\n\ |
| 123 | +in accordance with the Specification. By using Provisioning Technology in such a manner and\n\ |
| 124 | +making it available in accordance with the Specification, you further acknowledge your\n\ |
| 125 | +agreement to, and the acquisition of all necessary rights to permit the following:\n\ |
| 126 | +\n\ |
| 127 | + 1. A series of actions may occur ("Provisioning Process") in which a user may execute\n\ |
| 128 | + the Provisioning Technology on a machine ("Target Machine") with the intent of installing,\n\ |
| 129 | + extending or updating the functionality of an Eclipse-based product.\n\ |
| 130 | + 2. During the Provisioning Process, the Provisioning Technology may cause third party\n\ |
| 131 | + Installable Software or a portion thereof to be accessed and copied to the Target Machine.\n\ |
| 132 | + 3. Pursuant to the Specification, you will provide to the user the terms and conditions that\n\ |
| 133 | + govern the use of the Installable Software ("Installable Software Agreement") and such\n\ |
| 134 | + Installable Software Agreement shall be accessed from the Target Machine in accordance\n\ |
| 135 | + with the Specification. Such Installable Software Agreement must inform the user of the\n\ |
| 136 | + terms and conditions that govern the Installable Software and must solicit acceptance by\n\ |
| 137 | + the end user in the manner prescribed in such Installable Software Agreement. Upon such\n\ |
| 138 | + indication of agreement by the user, the provisioning Technology will complete installation\n\ |
| 139 | + of the Installable Software.\n\ |
| 140 | +\n\ |
| 141 | +Cryptography\n\ |
| 142 | +\n\ |
| 143 | +Content may contain encryption software. The country in which you are\n\ |
| 144 | +currently may have restrictions on the import, possession, and use,\n\ |
| 145 | +and/or re-export to another country, of encryption software. BEFORE\n\ |
| 146 | +using any encryption software, please check the country's laws,\n\ |
| 147 | +regulations and policies concerning the import, possession, or use, and\n\ |
| 148 | +re-export of encryption software, to see if this is permitted.\n\ |
| 149 | +\n\ |
| 150 | +Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.\n |
| 151 | +########### end of license property ########################################## |
0 commit comments