diff --git a/.devtoolset-3-eclipse-rse.metadata b/.devtoolset-3-eclipse-rse.metadata new file mode 100644 index 0000000..77a09f1 --- /dev/null +++ b/.devtoolset-3-eclipse-rse.metadata @@ -0,0 +1 @@ +18d0dc512bad03a03107a794d8a45b9d6939f3b4 SOURCES/org.eclipse.tm-R3_6.tar.bz2 diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..4cb476c --- /dev/null +++ b/.gitignore @@ -0,0 +1 @@ +SOURCES/org.eclipse.tm-R3_6.tar.bz2 diff --git a/README.md b/README.md deleted file mode 100644 index 98f42b4..0000000 --- a/README.md +++ /dev/null @@ -1,4 +0,0 @@ -The master branch has no content - -Look at the c7 branch if you are working with CentOS-7, or the c4/c5/c6 branch for CentOS-4, 5 or 6 -If you find this file in a distro specific branch, it means that no content has been checked in yet diff --git a/SOURCES/eclipse-rse-commons-net-source.patch b/SOURCES/eclipse-rse-commons-net-source.patch new file mode 100644 index 0000000..66aa14a --- /dev/null +++ b/SOURCES/eclipse-rse-commons-net-source.patch @@ -0,0 +1,66 @@ +diff -up ./rse/features/org.eclipse.rse.telnet-feature/sourceTemplateFeature/feature.xml.fix2 ./rse/features/org.eclipse.rse.telnet-feature/sourceTemplateFeature/feature.xml +--- ./rse/features/org.eclipse.rse.telnet-feature/sourceTemplateFeature/feature.xml.fix2 2013-04-04 14:45:51.000000000 -0400 ++++ ./rse/features/org.eclipse.rse.telnet-feature/sourceTemplateFeature/feature.xml 2013-04-04 14:46:10.000000000 -0400 +@@ -34,13 +34,6 @@ + + + +- +- + + +- +- + + +- +- + + +- +- + + +- ++ + + + diff --git a/SOURCES/eclipse-rse-server-auth-pl.patch b/SOURCES/eclipse-rse-server-auth-pl.patch new file mode 100644 index 0000000..fdcc8fb --- /dev/null +++ b/SOURCES/eclipse-rse-server-auth-pl.patch @@ -0,0 +1,68 @@ +diff -up ./serverruntime/scripts/linux/auth.pl.fix ./serverruntime/scripts/linux/auth.pl +--- ./serverruntime/scripts/linux/auth.pl.fix 2011-12-01 15:38:49.000000000 -0500 ++++ ./serverruntime/scripts/linux/auth.pl 2011-12-01 15:39:30.000000000 -0500 +@@ -11,9 +11,12 @@ + # David McKnight (IBM) - [254785] [dstore] RSE Server assumes home directory on target machine + # David McKnight (IBM) - [262013] [dstore][unix] RSE Daemon fails to start server on HP-UX + # David McKnight (IBM) - [270833] Unify rseserver auth.pl to not use "su -p" on any Platform ++# Jeff Johnston (Red Hat) - [364859] Support Kerberos + #******************************************************************************* + + use Shell; ++use Authen::PAM; ++use POSIX qw(ttyname); + + if (!defined($ARGV[0]) || !defined($ARGV[1]) || !defined($ARGV[2]) || !defined($ARGV[3]) || !defined($ARGV[4])) + { +@@ -42,7 +45,23 @@ else + chomp($pwdIN); + + +- @passwdStruct = getpwnam($userIN); ++ @passwdStruct = getpwnam($userIN); ++ ++ sub my_conv_func { ++ my @res; ++ while ( @_ ) { ++ my $code = shift; ++ my $msg = shift; ++ my $ans = ""; ++ ++ $ans = $userIN if ($code == PAM_PROMPT_ECHO_ON() ); ++ $ans = $pwdIN if ($code == PAM_PROMPT_ECHO_OFF() ); ++ ++ push @res, (PAM_SUCCESS(),$ans); ++ } ++ push @res, PAM_SUCCESS(); ++ return @res; ++ } + + if (@passwdStruct == 0) + { +@@ -51,15 +70,21 @@ else + } + else + { +- $passwd=$passwdStruct[1]; + $dir=$passwdStruct[7]; # get the user's home dir +- #$passwd = $pass; +- +- $encryptedPWD = crypt($pwdIN, $passwd); ++ # now authenticate the password using Authen::PAM instead ++ # of using passwd in passwdStruct because it does not support ++ # kerberos ++ $service="login"; ++ $tty_name = ttyname(fileno(STDIN)); ++ ref($pamh = new Authen::PAM($service, $userIN, \&my_conv_func)) || ++ die "Error code $pamh during PAM init!"; ++ ++ $res = $pamh->pam_set_item(PAM_TTY(), $tty_name); ++ $res = $pamh->pam_authenticate; + $classpath=$ENV{CLASSPATH}; + $suOptions="-"; + +- if ($passwd eq $encryptedPWD) ++ if ($res == PAM_SUCCESS()) + { + print("success\n"); + diff --git a/SOURCES/eclipse-rse-server-scripts.patch b/SOURCES/eclipse-rse-server-scripts.patch new file mode 100644 index 0000000..2b84425 --- /dev/null +++ b/SOURCES/eclipse-rse-server-scripts.patch @@ -0,0 +1,77 @@ +diff -up ./serverruntime/data/ssl.properties.fix ./serverruntime/data/ssl.properties +--- ./serverruntime/data/ssl.properties.fix 2011-12-14 17:55:18.000000000 -0500 ++++ ./serverruntime/data/ssl.properties 2011-12-14 17:59:39.000000000 -0500 +@@ -38,7 +38,12 @@ disable_server_ssl=false + ################################### + # The keystore file and password need to be specified for the + # server to use. If none is specified, the server falls back +-# to use the same keystore and password as the daemon ++# to use the same keystore and password as the daemon. Note ++# that the server uses the home directory of the userid as its ++# working directory so a relative path will only work for both ++# daemon and server if the keystore file is copied. A full path ++# is required to share a single keystore file between server and ++# daemon. + # + #server_keystore_file= +-#server_keystore_password= +\ No newline at end of file ++#server_keystore_password= +diff -up ./serverruntime/scripts/linux/daemon.pl.fix ./serverruntime/scripts/linux/daemon.pl +--- ./serverruntime/scripts/linux/daemon.pl.fix 2011-12-05 18:58:17.000000000 -0500 ++++ ./serverruntime/scripts/linux/daemon.pl 2011-12-13 19:02:13.000000000 -0500 +@@ -43,16 +43,17 @@ else + $trace = $ENV{DSTORE_TRACING_ON}; + } + +- $dir= $ENV{PWD}; +- $plugins_dir=$dir; ++ $dir= "$ENV{PWD}"; ++ $configdir= "/etc/sysconfig/rseserver/"; ++ $plugins_dir="/usr/share/java/eclipse-rse-server"; + +- $ENV{A_PLUGIN_PATH}="$plugins_dir/"; ++ $ENV{A_PLUGIN_PATH}="$dir/"; + + + $oldClasspath = $ENV{CLASSPATH}; + + +- $ENV{CLASSPATH}="$plugins_dir:$plugins_dir/dstore_extra_server.jar:$plugins_dir/dstore_core.jar:$plugins_dir/dstore_miners.jar:$plugins_dir/clientserver.jar"; ++ $ENV{CLASSPATH}="$dir:$configdir:$plugins_dir/dstore_extra_server.jar:$plugins_dir/dstore_core.jar:$plugins_dir/dstore_miners.jar:$plugins_dir/clientserver.jar"; + if (defined ($oldClasspath)) + { + $ENV{CLASSPATH}="$ENV{CLASSPATH}:$oldClasspath"; +diff -up ./serverruntime/scripts/linux/server.pl.fix ./serverruntime/scripts/linux/server.pl +--- ./serverruntime/scripts/linux/server.pl.fix 2011-12-05 18:58:21.000000000 -0500 ++++ ./serverruntime/scripts/linux/server.pl 2011-12-06 18:16:23.000000000 -0500 +@@ -15,18 +15,17 @@ $port = $ARGV[0]; + $timeout = $ARGV[1]; + $clientUserID = $ARGV[2]; + +-$dir= $ENV{PWD}; +-#print("path $dir"); ++$dir="$ENV{PWD}"; ++$configdir="/etc/sysconfig/rseserver"; + +-#$plugins_dir=substr($dir,0,rindex($dir,"/")); +-$plugins_dir=$dir; ++$plugins_dir="/usr/share/java/eclipse-rse-server"; + + $ENV{A_PLUGIN_PATH}="$plugins_dir/"; + + $oldClasspath = $ENV{CLASSPATH}; + + +-$ENV{"CLASSPATH"}="$plugins_dir:$plugins_dir/dstore_extra_server.jar:$plugins_dir/dstore_core.jar:$plugins_dir/dstore_miners.jar:$plugins_dir/clientserver.jar:$oldClasspath"; ++$ENV{"CLASSPATH"}="$dir:$configdir:$plugins_dir:$plugins_dir/dstore_extra_server.jar:$plugins_dir/dstore_core.jar:$plugins_dir/dstore_miners.jar:$plugins_dir/clientserver.jar:$oldClasspath"; + + if (!defined($timeout)) + { +@@ -44,4 +43,4 @@ else + } + } + +-$ENV{CLASSPATH}=$oldClasspath; +\ No newline at end of file ++$ENV{CLASSPATH}=$oldClasspath; diff --git a/SOURCES/eclipse-rse-tm-repo.patch b/SOURCES/eclipse-rse-tm-repo.patch new file mode 100644 index 0000000..39d397c --- /dev/null +++ b/SOURCES/eclipse-rse-tm-repo.patch @@ -0,0 +1,22 @@ +diff -up ./releng/org.eclipse.tm.repo/category.xml.fix ./releng/org.eclipse.tm.repo/category.xml +--- ./releng/org.eclipse.tm.repo/category.xml.fix 2014-05-21 12:47:45.977219186 -0400 ++++ ./releng/org.eclipse.tm.repo/category.xml 2014-05-21 12:54:56.700518704 -0400 +@@ -15,6 +15,10 @@ + + + ++ ++ ++ ++ + + + diff --git a/SOURCES/eclipse-rse-top-pom.patch b/SOURCES/eclipse-rse-top-pom.patch new file mode 100644 index 0000000..550ae40 --- /dev/null +++ b/SOURCES/eclipse-rse-top-pom.patch @@ -0,0 +1,107 @@ +diff -up ./pom.xml.orig ./pom.xml +--- ./pom.xml.orig 2014-05-18 21:19:02.000000000 -0400 ++++ ./pom.xml 2014-05-21 12:44:05.257647123 -0400 +@@ -160,17 +160,24 @@ + + releng/org.eclipse.tm.repo + terminal/plugins/org.eclipse.tm.terminal ++ + terminal/plugins/org.eclipse.tm.terminal.view ++ ++ + terminal/features/org.eclipse.tm.terminal-feature ++ + terminal/features/org.eclipse.tm.terminal.view-feature ++ + + + +@@ -214,42 +222,7 @@ + + linux + gtk +- x86 +- +- +- linux +- gtk +- x86_64 +- +- +- linux +- gtk +- ppc64 +- +- +- win32 +- win32 +- x86 +- +- +- win32 +- win32 +- x86_64 +- +- +- macosx +- cocoa +- x86 +- +- +- macosx +- cocoa +- x86_64 +- +- +- aix +- gtk +- ppc ++ noarch + + + p2 +@@ -304,25 +277,8 @@ + org.eclipse.tycho + tycho-packaging-plugin + ${tycho-version} +- +- +- org.eclipse.tycho.extras +- tycho-buildtimestamp-jgit +- ${tycho-version} +- +- +- org.eclipse.tycho.extras +- tycho-sourceref-jgit +- ${tycho-extras-version} +- +- + + false +- jgit +- pom.xml +- +- true +- + + + diff --git a/SOURCES/epl-v10.html b/SOURCES/epl-v10.html new file mode 100644 index 0000000..9321f40 --- /dev/null +++ b/SOURCES/epl-v10.html @@ -0,0 +1,256 @@ + + + + + + +Eclipse Public License - Version 1.0 + + + +

Eclipse Public License - v 1.0

+ +

THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE +PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR +DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS +AGREEMENT.

+ +

1. DEFINITIONS

+ +

"Contribution" means:

+ +

a) in the case of the initial Contributor, the initial +code and documentation distributed under this Agreement, and

+

b) in the case of each subsequent Contributor:

+

i) changes to the Program, and

+

ii) additions to the Program;

+

where such changes and/or additions to the Program +originate from and are distributed by that particular Contributor. A +Contribution 'originates' from a Contributor if it was added to the +Program by such Contributor itself or anyone acting on such +Contributor's behalf. Contributions do not include additions to the +Program which: (i) are separate modules of software distributed in +conjunction with the Program under their own license agreement, and (ii) +are not derivative works of the Program.

+ +

"Contributor" means any person or entity that distributes +the Program.

+ +

"Licensed Patents" mean patent claims licensable by a +Contributor which are necessarily infringed by the use or sale of its +Contribution alone or when combined with the Program.

+ +

"Program" means the Contributions distributed in accordance +with this Agreement.

+ +

"Recipient" means anyone who receives the Program under +this Agreement, including all Contributors.

+ +

2. GRANT OF RIGHTS

+ +

a) Subject to the terms of this Agreement, each +Contributor hereby grants Recipient a non-exclusive, worldwide, +royalty-free copyright license to reproduce, prepare derivative works +of, publicly display, publicly perform, distribute and sublicense the +Contribution of such Contributor, if any, and such derivative works, in +source code and object code form.

+ +

b) Subject to the terms of this Agreement, each +Contributor hereby grants Recipient a non-exclusive, worldwide, +royalty-free patent license under Licensed Patents to make, use, sell, +offer to sell, import and otherwise transfer the Contribution of such +Contributor, if any, in source code and object code form. This patent +license shall apply to the combination of the Contribution and the +Program if, at the time the Contribution is added by the Contributor, +such addition of the Contribution causes such combination to be covered +by the Licensed Patents. The patent license shall not apply to any other +combinations which include the Contribution. No hardware per se is +licensed hereunder.

+ +

c) Recipient understands that although each Contributor +grants the licenses to its Contributions set forth herein, no assurances +are provided by any Contributor that the Program does not infringe the +patent or other intellectual property rights of any other entity. Each +Contributor disclaims any liability to Recipient for claims brought by +any other entity based on infringement of intellectual property rights +or otherwise. As a condition to exercising the rights and licenses +granted hereunder, each Recipient hereby assumes sole responsibility to +secure any other intellectual property rights needed, if any. For +example, if a third party patent license is required to allow Recipient +to distribute the Program, it is Recipient's responsibility to acquire +that license before distributing the Program.

+ +

d) Each Contributor represents that to its knowledge it +has sufficient copyright rights in its Contribution, if any, to grant +the copyright license set forth in this Agreement.

+ +

3. REQUIREMENTS

+ +

A Contributor may choose to distribute the Program in object code +form under its own license agreement, provided that:

+ +

a) it complies with the terms and conditions of this +Agreement; and

+ +

b) its license agreement:

+ +

i) effectively disclaims on behalf of all Contributors +all warranties and conditions, express and implied, including warranties +or conditions of title and non-infringement, and implied warranties or +conditions of merchantability and fitness for a particular purpose;

+ +

ii) effectively excludes on behalf of all Contributors +all liability for damages, including direct, indirect, special, +incidental and consequential damages, such as lost profits;

+ +

iii) states that any provisions which differ from this +Agreement are offered by that Contributor alone and not by any other +party; and

+ +

iv) states that source code for the Program is available +from such Contributor, and informs licensees how to obtain it in a +reasonable manner on or through a medium customarily used for software +exchange.

+ +

When the Program is made available in source code form:

+ +

a) it must be made available under this Agreement; and

+ +

b) a copy of this Agreement must be included with each +copy of the Program.

+ +

Contributors may not remove or alter any copyright notices contained +within the Program.

+ +

Each Contributor must identify itself as the originator of its +Contribution, if any, in a manner that reasonably allows subsequent +Recipients to identify the originator of the Contribution.

+ +

4. COMMERCIAL DISTRIBUTION

+ +

Commercial distributors of software may accept certain +responsibilities with respect to end users, business partners and the +like. While this license is intended to facilitate the commercial use of +the Program, the Contributor who includes the Program in a commercial +product offering should do so in a manner which does not create +potential liability for other Contributors. Therefore, if a Contributor +includes the Program in a commercial product offering, such Contributor +("Commercial Contributor") hereby agrees to defend and +indemnify every other Contributor ("Indemnified Contributor") +against any losses, damages and costs (collectively "Losses") +arising from claims, lawsuits and other legal actions brought by a third +party against the Indemnified Contributor to the extent caused by the +acts or omissions of such Commercial Contributor in connection with its +distribution of the Program in a commercial product offering. The +obligations in this section do not apply to any claims or Losses +relating to any actual or alleged intellectual property infringement. In +order to qualify, an Indemnified Contributor must: a) promptly notify +the Commercial Contributor in writing of such claim, and b) allow the +Commercial Contributor to control, and cooperate with the Commercial +Contributor in, the defense and any related settlement negotiations. The +Indemnified Contributor may participate in any such claim at its own +expense.

+ +

For example, a Contributor might include the Program in a commercial +product offering, Product X. That Contributor is then a Commercial +Contributor. If that Commercial Contributor then makes performance +claims, or offers warranties related to Product X, those performance +claims and warranties are such Commercial Contributor's responsibility +alone. Under this section, the Commercial Contributor would have to +defend claims against the other Contributors related to those +performance claims and warranties, and if a court requires any other +Contributor to pay any damages as a result, the Commercial Contributor +must pay those damages.

+ +

5. NO WARRANTY

+ +

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS +PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS +OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, +ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY +OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely +responsible for determining the appropriateness of using and +distributing the Program and assumes all risks associated with its +exercise of rights under this Agreement , including but not limited to +the risks and costs of program errors, compliance with applicable laws, +damage to or loss of data, programs or equipment, and unavailability or +interruption of operations.

+ +

6. DISCLAIMER OF LIABILITY

+ +

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT +NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, +INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING +WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF +LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING +NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR +DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED +HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

+ +

7. GENERAL

+ +

If any provision of this Agreement is invalid or unenforceable under +applicable law, it shall not affect the validity or enforceability of +the remainder of the terms of this Agreement, and without further action +by the parties hereto, such provision shall be reformed to the minimum +extent necessary to make such provision valid and enforceable.

+ +

If Recipient institutes patent litigation against any entity +(including a cross-claim or counterclaim in a lawsuit) alleging that the +Program itself (excluding combinations of the Program with other +software or hardware) infringes such Recipient's patent(s), then such +Recipient's rights granted under Section 2(b) shall terminate as of the +date such litigation is filed.

+ +

All Recipient's rights under this Agreement shall terminate if it +fails to comply with any of the material terms or conditions of this +Agreement and does not cure such failure in a reasonable period of time +after becoming aware of such noncompliance. If all Recipient's rights +under this Agreement terminate, Recipient agrees to cease use and +distribution of the Program as soon as reasonably practicable. However, +Recipient's obligations under this Agreement and any licenses granted by +Recipient relating to the Program shall continue and survive.

+ +

Everyone is permitted to copy and distribute copies of this +Agreement, but in order to avoid inconsistency the Agreement is +copyrighted and may only be modified in the following manner. The +Agreement Steward reserves the right to publish new versions (including +revisions) of this Agreement from time to time. No one other than the +Agreement Steward has the right to modify this Agreement. The Eclipse +Foundation is the initial Agreement Steward. The Eclipse Foundation may +assign the responsibility to serve as the Agreement Steward to a +suitable separate entity. Each new version of the Agreement will be +given a distinguishing version number. The Program (including +Contributions) may always be distributed subject to the version of the +Agreement under which it was received. In addition, after a new version +of the Agreement is published, Contributor may elect to distribute the +Program (including its Contributions) under the new version. Except as +expressly stated in Sections 2(a) and 2(b) above, Recipient receives no +rights or licenses to the intellectual property of any Contributor under +this Agreement, whether expressly, by implication, estoppel or +otherwise. All rights in the Program not expressly granted under this +Agreement are reserved.

+ +

This Agreement is governed by the laws of the State of New York and +the intellectual property laws of the United States of America. No party +to this Agreement will bring a legal action under this Agreement more +than one year after the cause of action arose. Each party waives its +rights to a jury trial in any resulting litigation.

+ + \ No newline at end of file diff --git a/SOURCES/notice.html b/SOURCES/notice.html new file mode 100644 index 0000000..f19c483 --- /dev/null +++ b/SOURCES/notice.html @@ -0,0 +1,108 @@ + + + + + +Eclipse Foundation Software User Agreement + + + +

Eclipse Foundation Software User Agreement

+

February 1, 2011

+ +

Usage Of Content

+ +

THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS + (COLLECTIVELY "CONTENT"). 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 AGREE THAT YOUR USE + OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR + NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND + CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT USE THE CONTENT.

+ +

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 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.

+ +

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").

+ +
    +
  • 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").
  • +
  • Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java™ ARchive) in a directory named "plugins".
  • +
  • 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 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.
  • +
+ +

The terms and conditions governing Plug-ins and Fragments should be contained in files named "about.html" ("Abouts"). The terms and conditions governing Features and +Included Features should be contained in files named "license.html" ("Feature Licenses"). 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
  • +
  • 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 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. +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.

+ +

THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE +OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):

+ + + +

IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License is provided, please +contact the Eclipse Foundation to determine what terms and conditions 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 the purpose of allowing users to install software, documentation, information and/or + other materials (collectively "Installable Software"). 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").

+ +

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 Installable Software to be presented to, and accepted by, the users of the Provisioning Technology + in accordance with the Specification. By using Provisioning Technology in such a manner and 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, extending or updating the functionality of an Eclipse-based + product.
  2. +
  3. 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.
  4. +
  5. 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 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 the end user in the manner prescribed in such Installable Software Agreement. Upon such + indication of agreement by the user, the provisioning Technology will complete installation of the Installable Software.
  6. +
+ +

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, regulations and policies concerning the import, + possession, or use, and re-export of encryption software, to see if this is permitted.

+ +

Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.

+ + diff --git a/SPECS/eclipse-rse.spec b/SPECS/eclipse-rse.spec new file mode 100644 index 0000000..4b3ca80 --- /dev/null +++ b/SPECS/eclipse-rse.spec @@ -0,0 +1,296 @@ +%{?scl:%scl_package eclipse-rse} +%{!?scl:%global pkg_name %{name}} +%{!?maven_scl:%global maven_scl_prefix %{nil}} + +%global install_loc %{_datadir}/eclipse/dropins/rse +%global rseserver_install %{_datadir}/eclipse-rse-server +%global rseserver_java %{_datadir}/java/eclipse-rse-server +%global rseserver_config %{_sysconfdir}/sysconfig/rseserver +%global rse_snapshot org.eclipse.tm +%global rse_tag R3_6 + +Name: %{?scl_prefix}eclipse-rse +Summary: Eclipse Remote System Explorer +Version: 3.6 +Release: 4%{?dist} +License: EPL +URL: http://www.eclipse.org/dsdp/tm/ + +Source0: http://git.eclipse.org/c/tm/org.eclipse.tm.git/snapshot/org.eclipse.tm-%{rse_tag}.tar.bz2 +Source4: notice.html +Source5: epl-v10.html + +# Use Authen::pam to authenticate clients +Patch1: eclipse-rse-server-auth-pl.patch +# Fix classpath in daemon and server scripts to point +# to install locations +Patch2: eclipse-rse-server-scripts.patch +# Patch to remove eclipse-parent pom reference and multiple environments +Patch3: eclipse-rse-top-pom.patch +# Patch to remove dependency on org.apache.commons.net.source +Patch4: eclipse-rse-commons-net-source.patch +# Patch to allow junit4 to be used for building tests +Patch5: eclipse-rse-junit.patch +# Patch to remove tests from tm repo +Patch6: eclipse-rse-tm-repo.patch + +BuildRequires: java-1.7.0-openjdk-devel +# All arches line up except i386 -> x86 +%ifarch %{ix86} +%define eclipse_arch x86 +%else +%ifarch %{arm} +%define eclipse_arch arm +%else +%define eclipse_arch %{_arch} +%endif +%endif + +BuildArch: noarch + +BuildRequires: tycho +BuildRequires: tycho-extras +BuildRequires: %{maven_scl_prefix}maven-clean-plugin +BuildRequires: %{?scl_prefix}objectweb-asm +BuildRequires: %{?scl_prefix}feclipse-maven-plugin +BuildRequires: junit + +BuildRequires: %{?scl_prefix}eclipse-pde >= 1:3.8.0-0.21 +BuildRequires: %{?scl_prefix}eclipse-emf-core >= 0:2.4.1 +BuildRequires: %{?scl_prefix}eclipse-license +BuildRequires: apache-commons-net +Requires: %{?scl_prefix}eclipse-platform >= 1:3.8.0-0.21 +Requires: %{?scl_prefix}eclipse-emf-core >= 0:2.4.1 +Requires: apache-commons-net >= 0:2.0 + +Group: Development/Tools + +%description +Remote System Explorer (RSE) is a framework and toolkit in Eclipse Workbench +that allows you to connect and work with a variety of remote systems. + +%package server +Summary: Eclipse Remote System Explorer Server +Group: Development/Tools +Requires: perl +Requires: %{?scl_prefix}perl-Authen-PAM +Requires: java + +%description server +The Remote System Explorer (RSE) framework server that can be used so clients can connect to this machine via RSE. + +%prep +%setup -q -n org.eclipse.tm-%{rse_tag} + +%patch3 +%patch4 +%patch5 +%patch6 + +sed -i -e 's/x86<\/arch>/%{eclipse_arch}<\/arch>/g' pom.xml + +pushd rse/plugins/org.eclipse.rse.services.dstore +%patch1 +%patch2 +popd +sed -i -e 's|3.2,3.3|3.2,3.9|g' pom.xml + +%build + +export MAVEN_OPTS="-XX:CompileCommand=exclude,org/eclipse/tycho/core/osgitools/EquinoxResolver,newState ${MAVEN_OPTS}" +scl enable %{scl} - <<"EOF" +xmvn -o -DskipTychoVersionCheck -Dmaven.test.skip=true clean install +EOF + +cp %{SOURCE4} . +cp %{SOURCE5} . + +%install +scl enable %{scl} - <<"EOF" +install -d -m 755 %{buildroot}%{_datadir}/eclipse +install -d -m 755 %{buildroot}%{install_loc}/eclipse +install -d -m 755 %{buildroot}%{rseserver_install} +install -d -m 755 %{buildroot}%{rseserver_java} +install -d -m 755 %{buildroot}%{rseserver_config} + +xmvn -o org.fedoraproject:feclipse-maven-plugin:install -DsourceRepo=releng/org.eclipse.tm.repo/target/repository -DtargetLocation=%{buildroot}%{install_loc}/eclipse + +pushd %{buildroot}%{install_loc}/eclipse/plugins +rm org.apache.commons.net_*.jar +ln -s %{_root_datadir}/java/commons-net.jar org.apache.commons.net.jar +popd + +pushd %{buildroot}%{install_loc}/eclipse/plugins +unzip -q -o -d %{buildroot}%{rseserver_java} org.eclipse.rse.services.dstore_*.jar dstore_miners.jar +unzip -q -o -d %{buildroot}%{rseserver_java} org.eclipse.dstore.core_*.jar dstore_core.jar +unzip -q -o -d %{buildroot}%{rseserver_java} org.eclipse.dstore.extra_*.jar dstore_extra_server.jar +unzip -q -o -d %{buildroot}%{rseserver_java} org.eclipse.rse.services_*.jar clientserver.jar +# Remove server-specific jar files from plug-ins +jarname=`ls org.eclipse.rse.services.dstore_*.jar` +zip -d $jarname dstore_miners.jar +jarname=`ls org.eclipse.dstore.core_*.jar` +zip -d $jarname dstore_core.jar +jarname=`ls org.eclipse.dstore.extra_*.jar` +zip -d $jarname dstore_extra_server.jar +jarname=`ls org.eclipse.rse.services_*.jar` +zip -d $jarname clientserver.jar +popd + +pushd rse/plugins/org.eclipse.rse.services.dstore +pushd serverruntime/scripts/linux +cp *.pl %{buildroot}%{rseserver_install} +popd +pushd serverruntime/data +cp *.properties %{buildroot}%{rseserver_config} +cp *.dat %{buildroot}%{rseserver_install} +popd +EOF + +%files +%{install_loc} +%doc releng/rootfiles/epl-v10.html +%doc releng/rootfiles/notice.html + +%files server +%{rseserver_install} +%{rseserver_java} +%dir %{rseserver_config} +%config(noreplace) %{rseserver_config}/ssl.properties +%config(noreplace) %{rseserver_config}/rsecomm.properties +%doc notice.html +%doc epl-v10.html + +%changelog +* Wed Jul 16 2014 Sami Wagiaalla 3.6-4 +- Remove R on devtoolset-3-apache-commons-net which does not exist. + +* Tue Jul 15 2014 Sami Wagiaalla 3.6-2 +- Rebuild with apache-commons-net fix. + +* Mon Jul 14 2014 Jeff Johnston 3.6-1 +- Update to Luna SR0 (RSE 3.6) + +* Tue Jun 3 2014 Alexander Kurtakov 3.6-0.4.RC1 +- Use feclipse-maven-plugin to install. + +* Wed May 28 2014 Jeff Johnston 3.6-0.3.RC1 +- Fix link to commons-net.jar + +* Wed May 21 2014 Jeff Johnston 3.6-0.2.RC1 +- Fix Requires for apache-commons-net + +* Wed May 21 2014 Jeff Johnston 3.6-0.1.RC1 +- Update to 3.6 RC1 + +* Mon May 19 2014 Jeff Johnston 3.5.1-0.2.RC4 +- Use maven_scl_prefix for maven BuildRequires + +* Thu Oct 10 2013 Jeff Johnston 3.5.1-0.1.RC4 +- Update to 3.5.1 RC4 used for Kepler SR1 + +* Wed Oct 9 2013 Krzysztof Daniel 3.5-2 +- Update to Kepler SR1 + +* Mon Jul 1 2013 Alexander Kurtakov 3.5-1 +- Update to Kepler final. + +* Fri Jun 7 2013 Alexander Kurtakov 3.5-0.4.rc3 +- Update to Kepler RC3. + +* Wed Apr 10 2013 Alexander Kurtakov 3.5-0.3.m6 +- Dependency on auth pam needs to be scl-ized too. + +* Wed Apr 10 2013 Alexander Kurtakov 3.5-0.2.m6 +- Build against sclized apache-commons-net. +- Fix features to install in features folder. + +* Fri Apr 05 2013 Jeff Johnston 3.5-0.1.m6 +- Update rse to 3.5M6 which is what was shipped for Kepler M6. +- Need to use full git tree and tycho to build. + +* Tue Jan 8 2013 Krzysztof Daniel 3.4-7 +- Require sclized perl auth. + +* Wed Dec 12 2012 Roland Grunberg 3.4-6 +- Change from ExclusiveArch to BuildArch noarch. + +* Wed Dec 12 2012 Krzysztof Daniel 3.4-5 +- Depend on SCLized apache-commons-net. + +* Thu Nov 29 2012 Alexander Kurtakov 3.4-4 +- SCL-ize. + +* Wed Jul 18 2012 Fedora Release Engineering - 3.4-3 +- Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild + +* Fri Jul 6 2012 Alexander Kurtakov 3.4-2 +- Fix the commons-net link for rawhide. + +* Thu Jul 05 2012 Jeff Johnston - 3.4-1 +- Update to RSE 3.4 + +* Wed May 2 2012 Alexander Kurtakov 3.3.1-2 +- Use apache-commons-net instead of jakarta-commons-net. +- Drop old stuff. + +* Mon Apr 02 2012 Jeff Johnston - 3.3.1-1 +- Update to RSE 3.3.1 + +* Fri Jan 13 2012 Fedora Release Engineering - 3.3-5 +- Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass_Rebuild + +* Wed Dec 28 2011 Orion Poplawski 3.3-4 +- Build org.eclipse.rse.useractions feature + +* Wed Dec 14 2011 Jeff Johnston 3.3-3 +- Create server sub-package +- Remove nested jars from plug-ins +- Remove reconciler %%post and %%postun sections +- Bump release + +* Mon Nov 28 2011 Jeff Johnston 3.3-1 +- Upgrade to RSE 3.3 + +* Wed Oct 5 2011 Sami Wagiaalla 3.2-4 +- Use the reconciler to install/uninstall plugins during rpm + post and postun respectively. + +* Tue Feb 08 2011 Fedora Release Engineering - 3.2-3 +- Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild + +* Wed Jan 5 2011 Alexander Kurtakov 3.2-2 +- Fix broken symlink. + +* Fri Jul 9 2010 Alexander Kurtakov 3.2-1 +- Update to 3.2 (Helios). + +* Fri Mar 19 2010 Jeff Johnston 3.1.2-1 +- Rebase to 3.1.2 (Galileo SR2 version). + +* Thu Feb 25 2010 Jeff Johnston 3.1.1-3 +- Resolves: #567874 +- Remove oro requirement as it is not needed. + +* Tue Oct 27 2009 Jeff Johnston 3.1.1-2 +- Update plugin and feature version property files. + +* Tue Oct 20 2009 Jeff Johnston 3.1.1-1 +- Move to 3.1.1 tarball. + +* Fri Aug 21 2009 Jeff Johnston 3.1-2 +- Add BuildArch noarch. + +* Mon Aug 17 2009 Jeff Johnston 3.1-1 +- Move to 3.1 tarball. + +* Wed Jul 29 2009 Jeff Johnston 3.0.3-4 +- Resolves #514630 + +* Tue Jul 28 2009 Jeff Johnston 3.0.3-3 +- Restrict arch support to those supported by prereq CDT. + +* Fri Jul 24 2009 Fedora Release Engineering - 3.0.3-2 +- Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild + +* Thu Jul 23 2009 Jeff Johnston 3.0.3-1 +- Initial release.