Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSravan Kumar Lakkimsetti2017-06-09 09:27:27 -0400
committerSravan Kumar Lakkimsetti2017-06-09 09:27:27 -0400
commitf1f0938f71f7ad73f707593f17c767edc951cbe5 (patch)
tree57ca7af0a35f9cdccfe7d820787899fea937e339 /eclipse.platform.releng.tychoeclipsebuilder/rcp.sdk
parent19c077dcd09452460a432e42cc35c514d2a84477 (diff)
downloadeclipse.platform.releng.aggregator-f1f0938f71f7ad73f707593f17c767edc951cbe5.tar.gz
eclipse.platform.releng.aggregator-f1f0938f71f7ad73f707593f17c767edc951cbe5.tar.xz
eclipse.platform.releng.aggregator-f1f0938f71f7ad73f707593f17c767edc951cbe5.zip
Bug 517929 - Update POMs in the master for 4.8 release
Change-Id: I94a66ff2d40779af12a58f29a776c5f048a00b60 Signed-off-by: Sravan Kumar Lakkimsetti <sravankumarl@in.ibm.com>
Diffstat (limited to 'eclipse.platform.releng.tychoeclipsebuilder/rcp.sdk')
-rw-r--r--eclipse.platform.releng.tychoeclipsebuilder/rcp.sdk/pom.xml4
-rw-r--r--eclipse.platform.releng.tychoeclipsebuilder/rcp.sdk/rcp.sdk.product68
2 files changed, 35 insertions, 37 deletions
diff --git a/eclipse.platform.releng.tychoeclipsebuilder/rcp.sdk/pom.xml b/eclipse.platform.releng.tychoeclipsebuilder/rcp.sdk/pom.xml
index f7d66c58..a8e4a753 100644
--- a/eclipse.platform.releng.tychoeclipsebuilder/rcp.sdk/pom.xml
+++ b/eclipse.platform.releng.tychoeclipsebuilder/rcp.sdk/pom.xml
@@ -19,11 +19,11 @@
<parent>
<groupId>eclipse.platform.releng.tychoeclipsebuilder</groupId>
<artifactId>eclipse.platform.releng.tychoeclipsebuilder</artifactId>
- <version>4.7.0-SNAPSHOT</version>
+ <version>4.8.0-SNAPSHOT</version>
</parent>
<artifactId>org.eclipse.rcp.sdk.id</artifactId>
- <version>4.7.0-SNAPSHOT</version>
+ <version>4.8.0-SNAPSHOT</version>
<packaging>eclipse-repository</packaging>
<build>
diff --git a/eclipse.platform.releng.tychoeclipsebuilder/rcp.sdk/rcp.sdk.product b/eclipse.platform.releng.tychoeclipsebuilder/rcp.sdk/rcp.sdk.product
index d7400fa2..87482af2 100644
--- a/eclipse.platform.releng.tychoeclipsebuilder/rcp.sdk/rcp.sdk.product
+++ b/eclipse.platform.releng.tychoeclipsebuilder/rcp.sdk/rcp.sdk.product
@@ -1,15 +1,18 @@
<?xml version="1.0" encoding="UTF-8"?>
<?pde version="3.5"?>
-<product name="Eclipse RCP SDK" uid="org.eclipse.rcp.sdk.id" version="4.7.0.qualifier" useFeatures="true" includeLaunchers="true">
+<product name="Eclipse RCP SDK" uid="org.eclipse.rcp.sdk.id" version="4.8.0.qualifier" useFeatures="true" includeLaunchers="true">
<configIni use="default">
</configIni>
<launcherArgs>
- <programArgs> --launcher.appendVmargs</programArgs>
- <vmArgs>-Xms40m -Xmx384m</vmArgs>
- <vmArgsMac>-Xdock:icon=../Resources/Eclipse.icns -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts</vmArgsMac>
+ <programArgs>--launcher.appendVmargs
+ </programArgs>
+ <vmArgs>-Xms40m -Xmx384m
+ </vmArgs>
+ <vmArgsMac>-Xdock:icon=../Resources/Eclipse.icns -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts
+ </vmArgsMac>
</launcherArgs>
<windowImages/>
@@ -17,11 +20,6 @@
<launcher name="eclipse">
<linux icon="icons/icon.xpm"/>
<macosx icon="icons/Eclipse.icns"/>
- <solaris
- solarisLarge="icons/solaris/Eclipse.l.pm"
- solarisMedium="icons/solaris/Eclipse.m.pm"
- solarisSmall="icons/solaris/Eclipse.s.pm"
- solarisTiny="icons/solaris/Eclipse.t.pm"/>
<win useIco="true">
<ico path="icons/eclipse.ico"/>
<bmp/>
@@ -34,13 +32,13 @@
<license>
<url>http://eclipse.org/legal/epl/notice.php</url>
<text>
-Eclipse Foundation Software User Agreement
+ Eclipse Foundation Software User Agreement
April 9, 2014
Usage Of Content
THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR
-OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").
+OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY &quot;CONTENT&quot;).
USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS
AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR
NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU
@@ -55,47 +53,47 @@ Applicable Licenses
Unless otherwise indicated, all Content made available by the
Eclipse Foundation is provided to you under the terms and conditions of
-the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is
+the Eclipse Public License Version 1.0 (&quot;EPL&quot;). A copy of the EPL is
provided with this Content and is also available at http://www.eclipse.org/legal/epl-v10.html.
-For purposes of the EPL, "Program" will mean the Content.
+For purposes of the EPL, &quot;Program&quot; will mean the Content.
Content includes, but is not limited to, source code, object code,
documentation and other files maintained in the Eclipse Foundation source code
-repository ("Repository") in software modules ("Modules") and made available
-as downloadable archives ("Downloads").
+repository (&quot;Repository&quot;) in software modules (&quot;Modules&quot;) and made available
+as downloadable archives (&quot;Downloads&quot;).
- Content may be structured and packaged into modules to facilitate delivering,
- extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"),
- plug-in fragments ("Fragments"), and features ("Features").
+ extending, and upgrading the Content. Typical modules may include plug-ins (&quot;Plug-ins&quot;),
+ plug-in fragments (&quot;Fragments&quot;), and features (&quot;Features&quot;).
- Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java(TM) ARchive)
- in a directory named "plugins".
+ in a directory named &quot;plugins&quot;.
- A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.
- Each Feature may be packaged as a sub-directory in a directory named "features".
- Within a Feature, files named "feature.xml" may contain a list of the names and version
+ Each Feature may be packaged as a sub-directory in a directory named &quot;features&quot;.
+ Within a Feature, files named &quot;feature.xml&quot; may contain a list of the names and version
numbers of the Plug-ins and/or Fragments associated with that Feature.
- - Features may also include other Features ("Included Features"). Within a Feature, files
- named "feature.xml" may contain a list of the names and version numbers of Included Features.
+ - Features may also include other Features (&quot;Included Features&quot;). Within a Feature, files
+ named &quot;feature.xml&quot; may contain a list of the names and version numbers of Included Features.
The terms and conditions governing Plug-ins and Fragments should be
-contained in files named "about.html" ("Abouts"). The terms and
+contained in files named &quot;about.html&quot; (&quot;Abouts&quot;). The terms and
conditions governing Features and Included Features should be contained
-in files named "license.html" ("Feature Licenses"). Abouts and Feature
+in files named &quot;license.html&quot; (&quot;Feature Licenses&quot;). Abouts and Feature
Licenses may be located in any directory of a Download or Module
including, but not limited to the following locations:
- The top-level (root) directory
- Plug-in and Fragment directories
- Inside Plug-ins and Fragments packaged as JARs
- - Sub-directories of the directory named "src" of certain Plug-ins
+ - Sub-directories of the directory named &quot;src&quot; of certain Plug-ins
- Feature directories
Note: if a Feature made available by the Eclipse Foundation is installed using the
-Provisioning Technology (as defined below), you must agree to a license ("Feature
-Update License") during the installation process. If the Feature contains
+Provisioning Technology (as defined below), you must agree to a license (&quot;Feature
+Update License&quot;) during the installation process. If the Feature contains
Included Features, the Feature Update License should either provide you
with the terms and conditions governing the Included Features or inform
you where you can locate them. Feature Update Licenses may be found in
-the "license" property of files named "feature.properties" found within a Feature.
+the &quot;license&quot; property of files named &quot;feature.properties&quot; found within a Feature.
Such Abouts, Feature Licenses, and Feature Update Licenses contain the
terms and conditions (or references to such terms and conditions) that
govern your use of the associated Content in that directory.
@@ -119,12 +117,12 @@ govern that particular Content.
Use of Provisioning Technology
The Eclipse Foundation makes available provisioning software, examples of which include,
-but are not limited to, p2 and the Eclipse Update Manager ("Provisioning Technology") for
+but are not limited to, p2 and the Eclipse Update Manager (&quot;Provisioning Technology&quot;) for
the purpose of allowing users to install software, documentation, information and/or
-other materials (collectively "Installable Software"). This capability is provided with
+other materials (collectively &quot;Installable Software&quot;). This capability is provided with
the intent of allowing such users to install, extend and update Eclipse-based products.
Information about packaging Installable Software is available at
-http://eclipse.org/equinox/p2/repository_packaging.html ("Specification").
+http://eclipse.org/equinox/p2/repository_packaging.html (&quot;Specification&quot;).
You may use Provisioning Technology to allow other parties to install Installable Software.
You shall be responsible for enabling the applicable license agreements relating to the
@@ -133,13 +131,13 @@ in accordance with the Specification. By using Provisioning Technology in such a
making it available in accordance with the Specification, you further acknowledge your
agreement to, and the acquisition of all necessary rights to permit the following:
- 1. A series of actions may occur ("Provisioning Process") in which a user may execute
- the Provisioning Technology on a machine ("Target Machine") with the intent of installing,
+ 1. A series of actions may occur (&quot;Provisioning Process&quot;) in which a user may execute
+ the Provisioning Technology on a machine (&quot;Target Machine&quot;) with the intent of installing,
extending or updating the functionality of an Eclipse-based product.
2. During the Provisioning Process, the Provisioning Technology may cause third party
Installable Software or a portion thereof to be accessed and copied to the Target Machine.
3. Pursuant to the Specification, you will provide to the user the terms and conditions that
- govern the use of the Installable Software ("Installable Software Agreement") and such
+ govern the use of the Installable Software (&quot;Installable Software Agreement&quot;) and such
Installable Software Agreement shall be accessed from the Target Machine in accordance
with the Specification. Such Installable Software Agreement must inform the user of the
terms and conditions that govern the Installable Software and must solicit acceptance by
@@ -152,7 +150,7 @@ Cryptography
Content may contain encryption software. The country in which you are
currently may have restrictions on the import, possession, and use,
and/or re-export to another country, of encryption software. BEFORE
-using any encryption software, please check the country's laws,
+using any encryption software, please check the country&apos;s laws,
regulations and policies concerning the import, possession, or use, and
re-export of encryption software, to see if this is permitted.

Back to the top