1+ # ##############################################################################
2+ # Copyright (c) 2025 Christoph Läubrich and others.
3+ #
4+ # This program and the accompanying materials
5+ # are made available under the terms of the Eclipse Public License 2.0
6+ # which accompanies this distribution, and is available at
7+ # https://www.eclipse.org/legal/epl-2.0/
8+ #
9+ # SPDX-License-Identifier: EPL-2.0
10+ #
11+ # Contributors:
12+ # Christoph Läubrich - initial API and implementation
13+ # ##############################################################################
14+ featureName =Terminal Feature
15+ providerName =Eclipse.org
16+ description =Eclipse Platform Terminal Support.
17+ licenseURL =license.html
18+ license =\
19+ Eclipse Foundation Software User Agreement\n \
20+ \n \
21+ November 22, 2017\n \
22+ \n \
23+ Usage Of Content\n \
24+ \n \
25+ THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION\n \
26+ AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT"). USE OF\n \
27+ THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE\n \
28+ TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n \
29+ BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED\n \
30+ BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE\n \
31+ AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE\n \
32+ TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS OF ANY\n \
33+ APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU\n \
34+ MAY NOT USE THE CONTENT.\n \
35+ \n \
36+ Applicable Licenses\n \
37+ \n \
38+ Unless otherwise indicated, all Content made available by the Eclipse Foundation\n \
39+ is provided to you under the terms and conditions of the Eclipse Public License\n \
40+ Version 2.0 ("EPL"). A copy of the EPL is provided with this Content and is also\n \
41+ available at http://www.eclipse.org/legal/epl-2.0. For purposes of the EPL,\n \
42+ "Program" will mean the Content.\n \
43+ \n \
44+ Content includes, but is not limited to, source code, object code, documentation\n \
45+ and other files maintained in the Eclipse Foundation source code repository\n \
46+ ("Repository") in software modules ("Modules") and made available as\n \
47+ downloadable archives ("Downloads").\n \
48+ \n \
49+ - Content may be structured and packaged into modules to facilitate\n \
50+ delivering, extending, and upgrading the Content. Typical modules may\n \
51+ include plug-ins ("Plug-ins"), plug-in fragments ("Fragments"), and\n \
52+ features ("Features").\n \
53+ - Each Plug-in or Fragment may be packaged as a sub-directory or JAR\n \
54+ (Java\u2122 ARchive) in a directory named "plugins".\n \
55+ - A Feature is a bundle of one or more Plug-ins and/or Fragments and\n \
56+ associated material. Each Feature may be packaged as a sub-directory in a\n \
57+ directory named "features". Within a Feature, files named "feature.xml" may\n \
58+ contain a list of the names and version numbers of the Plug-ins and/or\n \
59+ Fragments associated with that Feature.\n \
60+ - Features may also include other Features ("Included Features"). Within a\n \
61+ Feature, files named "feature.xml" may contain a list of the names and\n \
62+ version numbers of Included Features.\n \
63+ \n \
64+ The terms and conditions governing Plug-ins and Fragments should be contained in\n \
65+ files named "about.html" ("Abouts"). The terms and conditions governing Features\n \
66+ and Included Features should be contained in files named "license.html"\n \
67+ ("Feature Licenses"). Abouts and Feature Licenses may be located in any\n \
68+ directory of a Download or Module including, but not limited to the following\n \
69+ locations:\n \
70+ \n \
71+ - The top-level (root) directory\n \
72+ - Plug-in and Fragment directories\n \
73+ - Inside Plug-ins and Fragments packaged as JARs\n \
74+ - Sub-directories of the directory named "src" of certain Plug-ins\n \
75+ - Feature directories\n \
76+ \n \
77+ Note: if a Feature made available by the Eclipse Foundation is installed using\n \
78+ the Provisioning Technology (as defined below), you must agree to a license\n \
79+ ("Feature Update License") during the installation process. If the Feature\n \
80+ contains Included Features, the Feature Update License should either provide you\n \
81+ with the terms and conditions governing the Included Features or inform you\n \
82+ where you can locate them. Feature Update Licenses may be found in the "license"\n \
83+ property of files named "feature.properties" found within a Feature. Such\n \
84+ Abouts, Feature Licenses, and Feature Update Licenses contain the terms and\n \
85+ conditions (or references to such terms and conditions) that govern your use of\n \
86+ the associated Content in that directory.\n \
87+ \n \
88+ THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL\n \
89+ OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE\n \
90+ OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n \
91+ \n \
92+ - Eclipse Public License Version 1.0 (available at\n \
93+ http://www.eclipse.org/legal/epl-v10.html)\n \
94+ - Eclipse Distribution License Version 1.0 (available at\n \
95+ http://www.eclipse.org/licenses/edl-v1.0.html)\n \
96+ - Common Public License Version 1.0 (available at\n \
97+ http://www.eclipse.org/legal/cpl-v10.html)\n \
98+ - Apache Software License 1.1 (available at\n \
99+ http://www.apache.org/licenses/LICENSE)\n \
100+ - Apache Software License 2.0 (available at\n \
101+ http://www.apache.org/licenses/LICENSE-2.0)\n \
102+ - Mozilla Public License Version 1.1 (available at\n \
103+ 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 TO\n \
106+ USE OF THE CONTENT. If no About, Feature License, or Feature Update License is\n \
107+ provided, please contact the Eclipse Foundation to determine what terms and\n \
108+ conditions govern that particular Content.\n \
109+ \n \
110+ Use of Provisioning Technology\n \
111+ \n \
112+ The Eclipse Foundation makes available provisioning software, examples of which\n \
113+ include, but are not limited to, p2 and the Eclipse Update Manager\n \
114+ ("Provisioning Technology") for the purpose of allowing users to install\n \
115+ software, documentation, information and/or other materials (collectively\n \
116+ "Installable Software"). This capability is provided with the intent of allowing\n \
117+ such users to install, extend and update Eclipse-based products. Information\n \
118+ about packaging Installable Software is available at\n \
119+ http://eclipse.org/equinox/p2/repository_packaging.html ("Specification").\n \
120+ \n \
121+ You may use Provisioning Technology to allow other parties to install\n \
122+ Installable Software. You shall be responsible for enabling the applicable\n \
123+ license agreements relating to the Installable Software to be presented to, and\n \
124+ accepted by, the users of the Provisioning Technology in accordance with the\n \
125+ Specification. By using Provisioning Technology in such a manner and making it\n \
126+ available in accordance with the Specification, you further acknowledge your\n \
127+ agreement to, and the acquisition of all necessary rights to permit the\n \
128+ following:\n \
129+ \n \
130+ 1. A series of actions may occur ("Provisioning Process") in which a user may\n \
131+ execute the Provisioning Technology on a machine ("Target Machine") with the\n \
132+ intent of installing, extending or updating the functionality of an\n \
133+ Eclipse-based product.\n \
134+ 2. During the Provisioning Process, the Provisioning Technology may cause third\n \
135+ party Installable Software or a portion thereof to be accessed and copied to\n \
136+ the Target Machine.\n \
137+ 3. Pursuant to the Specification, you will provide to the user the terms and\n \
138+ conditions that govern the use of the Installable Software ("Installable\n \
139+ Software Agreement") and such Installable Software Agreement shall be\n \
140+ accessed from the Target Machine in accordance with the Specification. Such\n \
141+ Installable Software Agreement must inform the user of the terms and\n \
142+ conditions that govern the Installable Software and must solicit acceptance\n \
143+ by the end user in the manner prescribed in such Installable\n \
144+ Software Agreement. Upon such indication of agreement by the user, the\n \
145+ provisioning Technology will complete installation of the\n \
146+ Installable Software.\n \
147+ \n \
148+ Cryptography\n \
149+ \n \
150+ Content may contain encryption software. The country in which you are currently\n \
151+ may have restrictions on the import, possession, and use, and/or re-export to\n \
152+ another country, of encryption software. BEFORE using any encryption software,\n \
153+ please check the country's laws, regulations and policies concerning the import,\n \
154+ possession, or use, and re-export of encryption software, to see if this is\n \
155+ permitted.\n \
156+ \n \
157+ Java and all Java-based trademarks are trademarks of Oracle Corporation in the\n \
158+ United States, other countries, or both.\n
159+ copyright =\
160+ Copyright (c) 2025 Christoph Läubrich and others.\n \
161+ \n \
162+ This program and the accompanying materials\n \
163+ are made available under the terms of the Eclipse Public License 2.0\n \
164+ which accompanies this distribution, and is available at\n \
165+ https://www.eclipse.org/legal/epl-2.0/\n \
166+ \n \
167+ SPDX-License-Identifier: EPL-2.0\n \
168+ \n \
169+ Contributors:\n \
170+ Christoph Läubrich - initial API and implementation\n
0 commit comments