[eclipse-rse] Create server sub-package Remove nested jars from plug-ins

Jeff Johnston jjohnstn at fedoraproject.org
Thu Dec 15 00:23:46 UTC 2011


commit 9ee6bd357c69b031912bc51928cc726aa143c17b
Author: Jeff Johnston <jjohnstn at redhat.com>
Date:   Wed Dec 14 19:16:07 2011 -0500

    Create server sub-package
    Remove nested jars from plug-ins

 eclipse-rse-server-auth-pl.patch |   68 ++++++++++
 eclipse-rse-server-scripts.patch |   77 ++++++++++++
 eclipse-rse.spec                 |   78 +++++++++++-
 epl-v10.html                     |  256 ++++++++++++++++++++++++++++++++++++++
 notice.html                      |  108 ++++++++++++++++
 5 files changed, 582 insertions(+), 5 deletions(-)
---
diff --git a/eclipse-rse-server-auth-pl.patch b/eclipse-rse-server-auth-pl.patch
new file mode 100644
index 0000000..fdcc8fb
--- /dev/null
+++ b/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/eclipse-rse-server-scripts.patch b/eclipse-rse-server-scripts.patch
new file mode 100644
index 0000000..2b84425
--- /dev/null
+++ b/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/eclipse-rse.spec b/eclipse-rse.spec
index 8d03409..47546f2 100644
--- a/eclipse-rse.spec
+++ b/eclipse-rse.spec
@@ -3,11 +3,14 @@
 %endif
 %global eclipse_base        %{_libdir}/eclipse
 %global install_loc         %{_datadir}/eclipse/dropins
+%global rseserver_install   %{_datadir}/eclipse-rse-server
+%global rseserver_java      %{_datadir}/java/eclipse-rse-server
+%global rseserver_config    %{_sysconfdir}/sysconfig/rseserver
 
 Name: eclipse-rse
 Summary: Eclipse Remote System Explorer
 Version: 3.3
-Release: 1%{?dist}
+Release: 3%{?dist}
 License: EPL
 URL: http://www.eclipse.org/dsdp/tm/
 
@@ -17,6 +20,14 @@ Source1: fetch-rse.sh
 # Following property files are generated by fetch-rse.sh.
 Source2: featureVersions.properties
 Source3: pluginVersions.properties
+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
 
 BuildRoot:  %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
 
@@ -41,14 +52,26 @@ Group: Development/Tools
 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: 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 -c
 
-%post
-eclipse-reconciler.sh %{_libdir}/eclipse %{_tmppath} > /dev/null
+cp %{SOURCE4} .
+cp %{SOURCE5} .
 
-%postun
-eclipse-reconciler.sh %{_libdir}/eclipse %{_tmppath} > /dev/null
+pushd org.eclipse.rse.services.dstore
+%patch1
+%patch2
+popd
 
 %build
 
@@ -75,6 +98,9 @@ popd
 rm -rf %{buildroot}
 install -d -m 755 %{buildroot}%{_datadir}/eclipse
 install -d -m 755 %{buildroot}%{install_loc}/rse
+install -d -m 755 %{buildroot}%{rseserver_install}
+install -d -m 755 %{buildroot}%{rseserver_java}
+install -d -m 755 %{buildroot}%{rseserver_config}
 
 unzip -q -o -d %{buildroot}%{install_loc}/rse \
  build/rpmBuild/org.eclipse.tm.terminal.zip
@@ -87,6 +113,32 @@ rm org.apache.commons.net_2.2.0*.jar
 ln -s %{_javadir}/commons-net.jar org.apache.commons.net_2.2.0.jar
 popd
 
+pushd %{buildroot}%{install_loc}/rse/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 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
+popd
+
 %clean
 rm -rf %{buildroot}
 
@@ -96,7 +148,23 @@ rm -rf %{buildroot}
 %doc org.eclipse.rse.sdk-feature/epl-v10.html
 %doc org.eclipse.rse.sdk-feature/license.html
 
+%files server
+%defattr(-,root,root,-)
+%{rseserver_install}
+%{rseserver_java}
+%{rseserver_config}
+%config(noreplace) %{rseserver_config}/ssl.properties
+%config(noreplace) %{rseserver_config}/rsecomm.properties
+%doc notice.html
+%doc epl-v10.html
+
 %changelog
+* Wed Dec 14 2011 Jeff Johnston <jjohnstn at redhat.com> 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 <swagiaal at redhat.com> 3.3-1
 - Upgrade to RSE 3.3
 
diff --git a/epl-v10.html b/epl-v10.html
new file mode 100644
index 0000000..9321f40
--- /dev/null
+++ b/epl-v10.html
@@ -0,0 +1,256 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head>
+
+
+
+
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Eclipse Public License - Version 1.0</title>
+
+<style type="text/css">
+  body {
+    size: 8.5in 11.0in;
+    margin: 0.25in 0.5in 0.25in 0.5in;
+    tab-interval: 0.5in;
+    }
+  p {  	
+    margin-left: auto;
+    margin-top:  0.5em;
+    margin-bottom: 0.5em;
+    }
+  p.list {
+  	margin-left: 0.5in;
+    margin-top:  0.05em;
+    margin-bottom: 0.05em;
+    }
+  </style></head><body lang="EN-US">
+
+<p align="center"><b>Eclipse Public License - v 1.0</b></p>
+
+<p>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.</p>
+
+<p><b>1. DEFINITIONS</b></p>
+
+<p>"Contribution" means:</p>
+
+<p class="list">a) in the case of the initial Contributor, the initial
+code and documentation distributed under this Agreement, and</p>
+<p class="list">b) in the case of each subsequent Contributor:</p>
+<p class="list">i) changes to the Program, and</p>
+<p class="list">ii) additions to the Program;</p>
+<p class="list">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.</p>
+
+<p>"Contributor" means any person or entity that distributes
+the Program.</p>
+
+<p>"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.</p>
+
+<p>"Program" means the Contributions distributed in accordance
+with this Agreement.</p>
+
+<p>"Recipient" means anyone who receives the Program under
+this Agreement, including all Contributors.</p>
+
+<p><b>2. GRANT OF RIGHTS</b></p>
+
+<p class="list">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.</p>
+
+<p class="list">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.</p>
+
+<p class="list">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.</p>
+
+<p class="list">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.</p>
+
+<p><b>3. REQUIREMENTS</b></p>
+
+<p>A Contributor may choose to distribute the Program in object code
+form under its own license agreement, provided that:</p>
+
+<p class="list">a) it complies with the terms and conditions of this
+Agreement; and</p>
+
+<p class="list">b) its license agreement:</p>
+
+<p class="list">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;</p>
+
+<p class="list">ii) effectively excludes on behalf of all Contributors
+all liability for damages, including direct, indirect, special,
+incidental and consequential damages, such as lost profits;</p>
+
+<p class="list">iii) states that any provisions which differ from this
+Agreement are offered by that Contributor alone and not by any other
+party; and</p>
+
+<p class="list">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.</p>
+
+<p>When the Program is made available in source code form:</p>
+
+<p class="list">a) it must be made available under this Agreement; and</p>
+
+<p class="list">b) a copy of this Agreement must be included with each
+copy of the Program.</p>
+
+<p>Contributors may not remove or alter any copyright notices contained
+within the Program.</p>
+
+<p>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.</p>
+
+<p><b>4. COMMERCIAL DISTRIBUTION</b></p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p><b>5. NO WARRANTY</b></p>
+
+<p>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.</p>
+
+<p><b>6. DISCLAIMER OF LIABILITY</b></p>
+
+<p>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.</p>
+
+<p><b>7. GENERAL</b></p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+</body></html>
\ No newline at end of file
diff --git a/notice.html b/notice.html
new file mode 100644
index 0000000..f19c483
--- /dev/null
+++ b/notice.html
@@ -0,0 +1,108 @@
+<?xml version="1.0" encoding="ISO-8859-1" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<title>Eclipse Foundation Software User Agreement</title>
+</head>
+
+<body lang="EN-US">
+<h2>Eclipse Foundation Software User Agreement</h2>
+<p>February 1, 2011</p>
+
+<h3>Usage Of Content</h3>
+
+<p>THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR 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 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.</p>
+
+<h3>Applicable Licenses</h3>
+
+<p>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
+   (&quot;EPL&quot;).  A copy of the EPL is provided with this Content and is also available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
+   For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
+
+<p>Content includes, but is not limited to, source code, object code, documentation and other files maintained in the Eclipse Foundation source code
+   repository (&quot;Repository&quot;) in software modules (&quot;Modules&quot;) and made available as downloadable archives (&quot;Downloads&quot;).</p>
+
+<ul>
+       <li>Content may be structured and packaged into modules to facilitate delivering, 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;).</li>
+       <li>Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java&trade; ARchive) in a directory named &quot;plugins&quot;.</li>
+       <li>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 &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.</li>
+       <li>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.</li>
+</ul>
+
+<p>The terms and conditions governing Plug-ins and Fragments should be 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 &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:</p>
+
+<ul>
+       <li>The top-level (root) directory</li>
+       <li>Plug-in and Fragment directories</li>
+       <li>Inside Plug-ins and Fragments packaged as JARs</li>
+       <li>Sub-directories of the directory named &quot;src&quot; of certain Plug-ins</li>
+       <li>Feature directories</li>
+</ul>
+
+<p>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 (&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 &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.</p>
+
+<p>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):</p>
+
+<ul>
+       <li>Eclipse Distribution License Version 1.0 (available at <a href="http://www.eclipse.org/licenses/edl-v10.html">http://www.eclipse.org/licenses/edl-v1.0.html</a>)</li>
+       <li>Common Public License Version 1.0 (available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>)</li>
+       <li>Apache Software License 1.1 (available at <a href="http://www.apache.org/licenses/LICENSE">http://www.apache.org/licenses/LICENSE</a>)</li>
+       <li>Apache Software License 2.0 (available at <a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>)</li>
+       <li>Metro Link Public License 1.00 (available at <a href="http://www.opengroup.org/openmotif/supporters/metrolink/license.html">http://www.opengroup.org/openmotif/supporters/metrolink/license.html</a>)</li>
+       <li>Mozilla Public License Version 1.1 (available at <a href="http://www.mozilla.org/MPL/MPL-1.1.html">http://www.mozilla.org/MPL/MPL-1.1.html</a>)</li>
+</ul>
+
+<p>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.</p>
+
+
+<h3>Use of Provisioning Technology</h3>
+
+<p>The Eclipse Foundation makes available provisioning software, examples of which include, 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 &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 <a
+       href="http://eclipse.org/equinox/p2/repository_packaging.html">http://eclipse.org/equinox/p2/repository_packaging.html</a>
+   (&quot;Specification&quot;).</p>
+
+<p>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:</p>
+
+<ol>
+       <li>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.</li>
+       <li>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.</li>
+       <li>Pursuant to the Specification, you will provide to the user the terms and conditions that 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 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.</li>
+</ol>
+
+<h3>Cryptography</h3>
+
+<p>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.</p>
+
+<p><small>Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.</small></p>
+</body>
+</html>


More information about the scm-commits mailing list