-
-Automated Testing of Eclipse Builds
-
-
-
- Automated Testing of Eclipse Builds
-
Last updated: March 2, 2011
Description
This document describes how to run Eclipse JUnit plugin tests from the command
- line using Eclipse SDK JUnit test plug-ins and a testing framework. This method of running tests is intended
- for anyone who wishes to automate their testing process or reproduce the testing
- mechanism used in Eclipse builds by the Eclipse Platform Release Engineering team.
Click here for a description of the testing
- framework, and how it can be used outside of the setup described here.
If you simply wish to write and run JUnit tests interactively from an Eclipse
- workbench, try one of the links below:
All test machines will require 1.4 and 1.5 java runtime environments installed to run all tests. See test targets
- for details on which tests require a 1.5 level jre. All other tests can be executed with either jre levels.
-
-
A properties file containing the following key-value pair: J2SE-5.0=<path to 1.5 java executable>. On Windows, the path must be enclosed with double quotes if it contains any space characters, e.g. J2SE-5.0="c:/program files/jdk1.5.0/jre/bin/java".
-
-
Info-ZIP UnZip version 5.41 or later installed and added to the path.
-
-
The JUnit Plugin Tests eclipse-Automated-Tests-<buildId>.zip from an Eclipse build (http://download.eclipse.org/eclipse/downloads/).
- This ZIP contains this document, scripts to run the tests, the test framework plug-ins and the JUnit test plug-ins.
-
-
An Eclipse SDK distribution (http://download.eclipse.org/eclipse/downloads/)
- to test. Usually you will want to test a particular Eclipse build using a matching
- Automated Tests feature.
-
-
To run the pde build tests you will need the eclipse-<buildId>delta-pack.zip.
-
-
To run the Team CVS tests you will need extssh access to a CVS repository.
- The tests create a lot of junk modules and tags so you will want to keep the
- test repository seperate from your development repository. While it is not necessary
- to clean up the repository between each Team test run you will probably want
- to clean it up periodically.
-
-
Some of the p2 tests require a copy of the Eclipse Platform Runtime Binary archive for the platform you
- are testing. More information is available from the Equinox Testing Wiki page.
-
-
-
Setup
-
-
Extract the eclipse-Automated-Tests-<buildId>.zip or tar.gz. On Window, extract this file close to the root of the drive to prevent some path names from exceeding
- the 255 character limit. This will create a top-level directory eclipse-testing.
-
-
Place the Eclipse SDK distribution to test (and the Eclipse Platform Runtime Binary) in the eclipse-testing directory.
- Do not extract these files as the test scripts will take care of this.
-
To run the Team CVS tests, edit the test.xml script to provide connection
- information. Replace the following strings in the teamcvs target of the test.xml file with the information described below:
-
-
@cvs_user@ - the account used to connect to the cvs repository
-
@cvs_password@ - the account password
@cvs_host@- the name of the cvs server
-
@cvs_root@ - the repository path
-
- These values are used at test time to automatically replace strings in
- org.eclipse.team.tests.cvs.core/repository.properties. For more information
- on how this file is used in the team CVS tests, click here.
-
-
-
To Run the PDE build scripts, save the eclipse-<buildId>delta-pack.zip to the eclipse-testing directory.
All parameters and targets are optional on windows systems with the exception of "-properties". On *nix systems, the os, ws and arch parameters
- must be specified in addition to the -properties parameter.
The JUnit test results are produced in individual xml files for each test plug-in with a test.xml. These
- results are copied to the eclipse-testing\results\xml directory. These results
- can be converted into html by running the "genHtml" target as described
- in the table below. Please be aware that "Build Successful" printed
- to the console is NOT indicative of tests passing.
-
-
-
Parameters
-
-
Parameter
Description
-
-
-os <operating system>
The OS the tests are being run on. One of: aix, hpux, linux, macosx, solaris,
- win32. Default win32
-
-
-ws <windowing system>
The windowing system the tests are being run on. One of: cocoa, gtk, photon,
- win32. Default win32
-
-
-arch <architecture>
The architecture the tests are being run on. One of: ppc, PA_RISC, x86,
- sparc. Default x86
-
-
-noclean
Run tests without installing a clean Eclipse (in "test-eclipse") between test targets. Default
- is to delete an existing test-eclipse directory and re-extract the Eclipse distribution between test targets.
-
-
-properties
As per requirements noted above, this is used to reference a properties file containing additional Ant properties
- used in running tests.Can be used to pass additional vm arguments to the
- Java virtual machine running the tests by adding the entry "extraVMargs=<the
- args to pass to the vm>" to the specified properties file.
At a minimum, the property file must include a "J2SE-5.0" property which specifies a path to a 1.5 java executable, for example:
The path must be enclosed in double quotes if it contains spaces. This key-value pair is required to run JUnit plug-in tests that require a 1.5 level jvm.
-
-
-vm
When runtests is executed, two instances of eclipse are started: one to invoke the org.eclipse.ant.core.antRunner application to run a test.xml script in a test plug-in (outer instance) and another in which the JUnit tests are being executed (inner). By default, both will use the java executable on the system path. The -vm property is used to specify an alternate java executable.
- For example, "-vm c:\jdk142\jre\bin\java".
However, the -vm value is ignored by the inner vm for JUnit plug-in tests requiring a 1.5 JRE to execute (see test targets). This property must be used in conjunction with the -properties parameter described above at all times.
-
-
-Dtest.target=performance
Runs the performance target only in each test plug-in's test.xml. When running tests on Windows,
- enclose this parameter in double quotes, ie. runtests "-Dtest.target=performance".
targetname1 targetname2 targetname3 etc..
Replace with a list of test targets to execute (space delineated). Each corresponds to an Ant target in the eclipse-testing/test.xml script.
For example, runtests -os linux -ws gtk -arch x86 ant antui -properties vm.properties This will execute the "ant" and "antui" test targets only. If not specified, the "all" target will be executed.
-
Appendix A - Test Targets
Ant targets in the main test.xml which execute tests. Typically each corresponds
- to the execution of a test plug-in's test.xml.
Target name (special jvm requirements)
Description / test plug-in
-
-
all (1.4, 1.5 and 1.6 JREs required)
Runs all the targets below. Default.
-
ant
org.eclipse.ant.tests.core
-
antui
org.eclipse.ant.tests.ui
-
compare
org.eclipse.compare.tests
-
coreexpressions
org.eclipse.core.expressions.tests
-
coreresources
org.eclipse.core.tests.resources
-
coreruntime
org.eclipse.core.tests.runtime
-
coretestsnet
org.eclipse.core.tests.net
-
equinoxsecurity
org.eclipse.equinox.security.tests
-
filebuffers
org.eclipse.core.filebuffers.tests
-
jdtapt (JRE 1.5 required)
org.eclipse.jdt.apt.tests
-
jdtaptpluggable (JRE 1.6 required)
org.eclipse.jdt.apt.pluggable.tests
-
jdtcompilerapt (JRE 1.6 required)
org.eclipse.jdt.compiler.apt.tests
-
jdtcompilertool (JRE 1.6 required)
org.eclipse.jdt.compiler.tool.tests
-
jdtcorebuilder (JRE 1.5 required)
org.eclipse.jdt.core.tests.builder
-
jdtcorecompiler (JRE 1.5 required)
org.eclipse.jdt.core.tests.compiler
-
jdtcoremodel (JRE 1.5 required)
org.eclipse.jdt.core.tests.model
-
jdtcoreperf
org.eclipse.jdt.core.tests.performance
-
jdtdebug
org.eclipse.jdt.debug.tests
-
jdttext
org.eclipse.jdt.text.tests
-
jdtui
org.eclipse.jdt.ui.tests
-
jdtuirefactoring
org.eclipse.jdt.ui.tests.refactoring
-
jface
org.eclipse.jface.text.tests
-
jfacedatabinding
org.eclipse.jface.tests.databinding
-
ltkcorerefactoringtests
org.eclipse.ltk.core.refactoring.tests
-
ltkuirefactoringtests
org.eclipse.ltk.ui.refactoring.tests
-
osgi
org.eclipse.osgi.tests
-
pdeapitooling (JRE 1.5 required)
org.eclipse.pde.api.tools.tests
-
pdebuild
org.eclipse.pde.build.tests
-
pdeui
org.eclipse.pde.ui.tests
-
relEng
org.eclipse.releng.tests
-
swt
org.eclipse.swt.tests
-
teamcore
org.eclipse.team.tests.core
-
teamcvs
org.eclipse.team.tests.cvs.core
-
text
org.eclipse.text.tests
-
ua
org.eclipse.ua.tests
-
ui
org.eclipse.ui.tests
-
uieditors
org.eclipse.ui.editors.tests
-
uiforms
org.eclipse.ui.tests.forms
-
uinavigator
org.eclipse.ui.tests.navigator
-
uiperformance
org.eclipse.ui.tests.performance
-
uircp
org.eclipse.ui.tests.rcp
-
uiviews
org.eclipse.ui.tests.views.properties.tabbed
-
uiworkbenchtexteditor
org.eclipse.ui.workbench.texteditor.tests
-
update
org.eclipse.update.tests.core
-
-
-
-
Appendix B - Supported os, ws, and arch
- value combinations
The following table contains the values that can be used with the -os, -ws,
- and -arch switches.
-
-
Operating System (os)
Windowing System (ws)
Architecture (arch)
-
-
hpux
motif
PA_RISC
-
-
linux
gtk
x86
-
-
linux
gtk
x86_64
-
-
macosx
carbox
ppc
-
-
macosx
cocoa
x86
-
-
macosx
cocoa
x86_64
-
-
solaris
gtk
sparc
-
-
solaris
gtk
x86
-
-
solaris
motif
sparc
-
-
win32
win32
x86
-
-
-
diff --git a/TMP/eclipse-junit-tests/src/main/scripts/runtests b/TMP/eclipse-junit-tests/src/main/scripts/runtests
deleted file mode 100755
index da0d6464d..000000000
--- a/TMP/eclipse-junit-tests/src/main/scripts/runtests
+++ /dev/null
@@ -1,87 +0,0 @@
-# !/bin/sh
-
-#set the DISPLAY for running tests on Linux
-DISPLAY=:0.0;export DISPLAY
-
-# by default, use the java executable on the path for outer and test jvm
-vmcmd=java
-
-#this value must be set when using rsh to execute this script, otherwise the script will execute from the user's home directory
-dir=.
-
-# operating system, windowing system and architecture variables
-os=
-ws=
-arch=
-
-# list of tests (targets) to execute in test.xml
-tests=
-
-# default value to determine if eclipse should be reinstalled between running of tests
-installmode="clean"
-
-# name of a property file to pass to Ant
-properties=
-
-# message printed to console
-usage="usage: $0 -os -ws -arch [-noclean] [][-properties ]"
-
-
-# proces command line arguments
-while [ $# -gt 0 ]
-do
- case "$1" in
- -dir) dir="$2"; shift;;
- -os) os="$2"; shift;;
- -ws) ws="$2"; shift;;
- -arch) arch="$2"; shift;;
- -noclean) installmode="noclean";;
- -properties) properties="-propertyfile $2";shift;;
- -vm) vmcmd="$2"; shift;;
- *) tests=$tests\ $1;;
- esac
- shift
-done
-
-# for *nix systems, os, ws and arch values must be specified
-if [ "x$os" = "x" ]
-then
- echo >&2 "$usage"
- exit 1
-fi
-
-if [ "x$ws" = "x" ]
-then
- echo >&2 "$usage"
- exit 1
-fi
-
-if [ "x$arch" = "x" ]
-then
- echo >&2 "$usage"
- exit 1
-fi
-
-#necessary when invoking this script through rsh
-cd $dir
-
-# verify os, ws and arch values passed in are valid before running tests
-if [ "$os-$ws-$arch" = "linux-gtk-x86" ] || [ "$os-$ws-$arch" = "macosx-cocoa-ppc" ] || [ "$os-$ws-$arch" = "macosx-cocoa-x86" ] || [ "$os-$ws-$arch" = "macosx-cocoa-x86_64" ] || [ "$os-$ws-$arch" = "aix-gtk-ppc" ] || [ "$os-$ws-$arch" = "aix-gtk-ppc64" ] || [ "$os-$ws-$arch" = "solaris-gtk-sparc" ] || [ "$os-$ws-$arch" = "solaris-gtk-x86" ] || [ "$os-$ws-$arch" = "linux-gtk-ppc64" ] || [ "$os-$ws-$arch" = "linux-gtk-ia64" ] || [ "$os-$ws-$arch" = "linux-gtk-x86_64" ] || [ "$os-$ws-$arch" = "hpux-gtk-ia64_32"]
-then
- if [ ! -r eclipse ]
- then
- tar -xzf eclipse-SDK-*.tar.gz
- unzip -qq -o -C eclipse-junit-tests-*.zip */plugins/org.eclipse.test* -d eclipse/dropins/
-fi
-
-# run tests
-launcher=`ls eclipse/plugins/org.eclipse.equinox.launcher_*.jar`
-$vmcmd -Dosgi.os=$os -Dosgi.ws=$ws -Dosgi.arch=$arch -jar $launcher -data workspace -application org.eclipse.ant.core.antRunner -file `pwd`/test.xml $tests -Dws=$ws -Dos=$os -Darch=$arch -D$installmode=true $properties -logger org.apache.tools.ant.DefaultLogger
-
-# display message to user if os, ws and arch are invalid
-else
- echo "The os, ws and arch values are either invalid or are an invalid combination"
-
-exit 1
-fi
-
diff --git a/TMP/eclipse-junit-tests/src/main/scripts/runtests.bat b/TMP/eclipse-junit-tests/src/main/scripts/runtests.bat
deleted file mode 100755
index f9a578deb..000000000
--- a/TMP/eclipse-junit-tests/src/main/scripts/runtests.bat
+++ /dev/null
@@ -1,63 +0,0 @@
-@echo off
-
-REM default java executable for outer and test vm
-set vmcmd=java
-set no_proxy=localhost,dev.eclipse.org,hudson.eclipse.org
-
-REM reset list of ant targets in test.xml to execute
-set tests=
-
-REM default switch to determine if eclipse should be reinstalled between running of tests
-set installmode=clean
-
-REM property file to pass to Ant scripts
-set properties=
-
-REM default values for os, ws and arch
-set os=win32
-set ws=win32
-set arch=x86
-
-REM reset ant command line args
-set ANT_CMD_LINE_ARGS=
-
-REM ****************************************************************
-REM
-REM Install Eclipse if it does not exist
-REM
-REM ****************************************************************
-if NOT EXIST eclipse unzip -qq -o eclipse-SDK-*.zip && unzip -qq -o -C eclipse-junit-tests*.zip plugins/org.eclipse.test* -d eclipse/dropins/
-
-
-:processcmdlineargs
-
-REM ****************************************************************
-REM
-REM Process command line arguments
-REM
-REM ****************************************************************
-
-if x%1==x goto run
-if x%1==x-ws set ws=%2 && shift && shift && goto processcmdlineargs
-if x%1==x-os set os =%2 && shift && shift && goto processcmdlineargs
-if x%1==x-arch set arch=%2 && shift && shift && goto processcmdlineargs
-if x%1==x-noclean set installmode=noclean&& shift && goto processcmdlineargs
-if x%1==x-properties set properties=-propertyfile %2 && shift && shift && goto processcmdlineargs
-if x%1==x-vm set vmcmd="%2" && shift && shift && goto processcmdlineargs
-
-set tests=%tests% %1 && shift && goto processcmdlineargs
-
-
-:run
-REM ***************************************************************************
-REM Run tests by running Ant in Eclipse on the test.xml script
-REM ***************************************************************************
-REM get name of org.eclipse.equinox.launcher_*.jar with version label
-dir /b eclipse\plugins\org.eclipse.equinox.launcher_*.jar>launcher-jar-name.txt
-set /p launcher-jar= -ws -arch [-noclean] [][-properties ]"
-
-
-# proces command line arguments
-while [ $# -gt 0 ]
-do
- case "$1" in
- -dir) dir="$2"; shift;;
- -os) os="$2"; shift;;
- -ws) ws="$2"; shift;;
- -arch) arch="$2"; shift;;
- -noclean) installmode="noclean";;
- -properties) properties="-propertyfile $2";shift;;
- -vm) vmcmd="$2"; shift;;
- *) tests=$tests\ $1;;
- esac
- shift
-done
-
-# for *nix systems, os, ws and arch values must be specified
-if [ "x$os" = "x" ]
-then
- echo >&2 "$usage"
- exit 1
-fi
-
-if [ "x$ws" = "x" ]
-then
- echo >&2 "$usage"
- exit 1
-fi
-
-if [ "x$arch" = "x" ]
-then
- echo >&2 "$usage"
- exit 1
-fi
-
-#necessary when invoking this script through rsh
-cd $dir
-
-# verify os, ws and arch values passed in are valid before running tests
-if [ "$os-$ws-$arch" = "linux-gtk-x86" ] || [ "$os-$ws-$arch" = "macosx-cocoa-ppc" ] || [ "$os-$ws-$arch" = "macosx-cocoa-x86" ] || [ "$os-$ws-$arch" = "aix-gtk-ppc" ] || [ "$os-$ws-$arch" = "aix-gtk-ppc64" ] || [ "$os-$ws-$arch" = "solaris-gtk-sparc" ] || [ "$os-$ws-$arch" = "solaris-gtk-x86" ] || [ "$os-$ws-$arch" = "linux-gtk-ppc64" ] || [ "$os-$ws-$arch" = "linux-gtk-ia64" ] || [ "$os-$ws-$arch" = "linux-gtk-x86_64" ] || [ "$os-$ws-$arch" = "hpux-gtk-ia64_32"]
-then
- if [ ! -r eclipse ]
- then
- tar -xzf eclipse-SDK-*.tar.gz
- unzip -qq -o -C eclipse-junit-tests-*.zip */plugins/org.eclipse.test* -d eclipse/dropins/
-fi
-
-# run tests
-launcher=`ls eclipse/plugins/org.eclipse.equinox.launcher_*.jar`
-$vmcmd -Dosgi.os=$os -Dosgi.ws=$ws -Dosgi.arch=$arch -jar $launcher -data workspace -application org.eclipse.ant.core.antRunner -file `pwd`/test.xml $tests -Dws=$ws -Dos=$os -Darch=$arch -D$installmode=true $properties -logger org.apache.tools.ant.DefaultLogger
-
-# display message to user if os, ws and arch are invalid
-else
- echo "The os, ws and arch values are either invalid or are an invalid combination"
-
-exit 1
-fi
-
diff --git a/TMP/eclipse-junit-tests/src/main/scripts/test.xml b/TMP/eclipse-junit-tests/src/main/scripts/test.xml
deleted file mode 100755
index a9d3b1661..000000000
--- a/TMP/eclipse-junit-tests/src/main/scripts/test.xml
+++ /dev/null
@@ -1,1015 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- -installIU ${extraIU} +
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- -installIU ${testPlugin} +
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- trying to find ${testPlugin}_*
-
-
-
-
- trying to find ${testPluginX}
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- trying to find ${testPlugin}_*
-
-
-
-
- trying to find ${testPluginX}
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/TMP/eclipse-junit-tests/testScripts/CVS/Entries b/TMP/eclipse-junit-tests/testScripts/CVS/Entries
deleted file mode 100644
index c4c3b9b2b..000000000
--- a/TMP/eclipse-junit-tests/testScripts/CVS/Entries
+++ /dev/null
@@ -1,5 +0,0 @@
-/readme.html/1.16/Tue Jun 7 13:22:45 2011/-kk/
-/runtests/1.34/Tue Jun 7 13:22:45 2011/-kb/
-/runtests.bat/1.10/Wed Jan 19 15:44:27 2011/-kk/
-/runtests.sh/1.7/Tue Jun 7 13:22:45 2011//
-/test.xml/1.213/Fri Nov 11 14:59:52 2011/-kk/
diff --git a/TMP/eclipse-junit-tests/testScripts/CVS/Repository b/TMP/eclipse-junit-tests/testScripts/CVS/Repository
deleted file mode 100644
index 533fddf26..000000000
--- a/TMP/eclipse-junit-tests/testScripts/CVS/Repository
+++ /dev/null
@@ -1 +0,0 @@
-org.eclipse.releng.eclipsebuilder/eclipse/buildConfigs/sdk.tests/testScripts
diff --git a/TMP/eclipse-junit-tests/testScripts/CVS/Root b/TMP/eclipse-junit-tests/testScripts/CVS/Root
deleted file mode 100644
index 2d37d165b..000000000
--- a/TMP/eclipse-junit-tests/testScripts/CVS/Root
+++ /dev/null
@@ -1 +0,0 @@
-:pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse
diff --git a/TMP/org.eclipse.sdk.epp/backup/org.eclipse.sdk.epp.product b/TMP/org.eclipse.sdk.epp/backup/org.eclipse.sdk.epp.product
deleted file mode 100644
index 7a8530264..000000000
--- a/TMP/org.eclipse.sdk.epp/backup/org.eclipse.sdk.epp.product
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
-
-
-
-
-
-
- -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/TMP/org.eclipse.sdk.epp/org.eclipse.sdk.epp.p2.inf b/TMP/org.eclipse.sdk.epp/org.eclipse.sdk.epp.p2.inf
deleted file mode 100755
index e6e60548a..000000000
--- a/TMP/org.eclipse.sdk.epp/org.eclipse.sdk.epp.p2.inf
+++ /dev/null
@@ -1,92 +0,0 @@
-instructions.configure=\
-addRepository(type:0,location:http${#58}//download.eclipse.org/eclipse/updates/4.2,name:The Eclipse Project Updates);\
-addRepository(type:1,location:http${#58}//download.eclipse.org/eclipse/updates/4.2,name:The Eclipse Project Updates);\
-addRepository(type:0,location:http${#58}//download.eclipse.org/e4/updates/0.12,name:e4 0.11 Updates);\
-addRepository(type:1,location:http${#58}//download.eclipse.org/e4/updates/0.12,name:e4 0.11 Updates);\
-addRepository(type:0,location:http${#58}//download.eclipse.org/releases/juno,name:Juno);\
-addRepository(type:1,location:http${#58}//download.eclipse.org/releases/juno,name:Juno);\
- mkdir(path:${installFolder}/dropins);
-requires.1.namespace=org.eclipse.equinox.p2.iu
-requires.1.name=toolingorg.eclipse.configuration.macosx
-requires.1.filter=(osgi.os=macosx)
-requires.1.range=[1.0.0,1.0.0]
-requires.1.greedy=true
-
-requires.2.namespace=org.eclipse.equinox.p2.iu
-requires.2.name=toolingorg.eclipse.configuration
-requires.2.filter=(!(osgi.os=macosx))
-requires.2.range=[1.0.0,1.0.0]
-requires.2.greedy=true
-
-requires.3.namespace=org.eclipse.equinox.p2.iu
-requires.3.name=toolingorg.eclipse.configuration.macosx.x86_64
-requires.3.filter=(&(osgi.os=macosx) (osgi.arch=x86_64))
-requires.3.range=[1.0.0,1.0.0]
-requires.3.greedy=true
-
-units.1.id=toolingorg.eclipse.configuration.macosx
-units.1.version=1.0.0
-units.1.provides.1.namespace=org.eclipse.equinox.p2.iu
-units.1.provides.1.name=toolingorg.eclipse.configuration.macosx
-units.1.provides.1.version=1.0.0
-units.1.filter=(osgi.os=macosx)
-units.1.touchpoint.id=org.eclipse.equinox.p2.osgi
-units.1.touchpoint.version=1.0.0
-units.1.instructions.configure=setProgramProperty(propName:osgi.instance.area.default,propValue:@user.home/Documents/workspace);
-units.1.instructions.unconfigure=setProgramProperty(propName:osgi.instance.area.default,propValue:);
-
-units.2.id=toolingorg.eclipse.configuration
-units.2.version=1.0.0
-units.2.provides.1.namespace=org.eclipse.equinox.p2.iu
-units.2.provides.1.name=toolingorg.eclipse.configuration
-units.2.provides.1.version=1.0.0
-units.2.filter=(!(osgi.os=macosx))
-units.2.touchpoint.id=org.eclipse.equinox.p2.osgi
-units.2.touchpoint.version=1.0.0
-units.2.instructions.configure=setProgramProperty(propName:osgi.instance.area.default,propValue:@user.home/workspace);
-units.2.instructions.unconfigure=setProgramProperty(propName:osgi.instance.area.default,propValue:);
-
-units.3.id=toolingorg.eclipse.configuration.macosx.x86_64
-units.3.version=1.0.0
-units.3.provides.1.namespace=org.eclipse.equinox.p2.iu
-units.3.provides.1.name=toolingorg.eclipse.configuration.macosx.x86_64
-units.3.provides.1.version=1.0.0
-units.3.filter=(&(osgi.os=macosx) (osgi.arch=x86_64))
-units.3.touchpoint.id=org.eclipse.equinox.p2.osgi
-units.3.touchpoint.version=1.0.0
-units.3.instructions.configure=addJvmArg(jvmArg:-Xms40m);addJvmArg(jvmArg:-Xmx512m);
-units.3.instructions.unconfigure=removeJvmArg(jvmArg:-Xms40m);removeJvmArg(jvmArg:-Xmx512m);
-
-requires.4.namespace=org.eclipse.equinox.p2.iu
-requires.4.name=toolingorg.eclipse.configuration.aix.ppc64
-requires.4.filter=(&(osgi.os=aix) (osgi.arch=ppc64))
-requires.4.range=[1.0.0,1.0.0]
-requires.4.greedy=true
-
-units.4.id=toolingorg.eclipse.configuration.aix.ppc64
-units.4.version=1.0.0
-units.4.provides.1.namespace=org.eclipse.equinox.p2.iu
-units.4.provides.1.name=toolingorg.eclipse.configuration.aix.ppc64
-units.4.provides.1.version=1.0.0
-units.4.filter=(&(osgi.os=aix) (osgi.arch=ppc64))
-units.4.touchpoint.id=org.eclipse.equinox.p2.osgi
-units.4.touchpoint.version=1.0.0
-units.4.instructions.configure=addJvmArg(jvmArg:-Xms40m);addJvmArg(jvmArg:-Xmx512m);
-units.4.instructions.unconfigure=removeJvmArg(jvmArg:-Xms40m);removeJvmArg(jvmArg:-Xmx512m);
-
-requires.5.namespace=org.eclipse.equinox.p2.iu
-requires.5.name=toolingorg.eclipse.configuration.gtk.linux.x86_64
-requires.5.filter=(&(osgi.os=linux) (osgi.arch=x86_64) (osgi.ws=gtk))
-requires.5.range=[1.0.0,1.0.0]
-requires.5.greedy=true
-
-units.5.id=toolingorg.eclipse.configuration.gtk.linux.x86_64
-units.5.version=1.0.0
-units.5.provides.1.namespace=org.eclipse.equinox.p2.iu
-units.5.provides.1.name=toolingorg.eclipse.configuration.gtk.linux.x86_64
-units.5.provides.1.version=1.0.0
-units.5.filter=(&(osgi.os=linux) (osgi.arch=x86_64) (osgi.ws=gtk))
-units.5.touchpoint.id=org.eclipse.equinox.p2.osgi
-units.5.touchpoint.version=1.0.0
-units.5.instructions.configure=setProgramProperty(propName:org.eclipse.swt.internal.gtk.useCairo,propValue:true);
-units.5.instructions.unconfigure=removeProgramProperty(propName:org.eclipse.swt.internal.gtk.useCairo);
\ No newline at end of file
diff --git a/TMP/org.eclipse.sdk.epp/org.eclipse.sdk.epp.product b/TMP/org.eclipse.sdk.epp/org.eclipse.sdk.epp.product
deleted file mode 100755
index 5793855b8..000000000
--- a/TMP/org.eclipse.sdk.epp/org.eclipse.sdk.epp.product
+++ /dev/null
@@ -1,182 +0,0 @@
-
-
-
-
-
-
-
-
-
- -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile
- -Xms40m -Xmx384m
- -Xdock:icon=../Resources/Eclipse.icns -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- http://eclipse.org/legal/epl/notice.php
-
- 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(TM) 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):
-
- - Eclipse Distribution License Version 1.0 (available at http://www.eclipse.org/licenses/edl-v1.0.html)
- - Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)
- - Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)
- - Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)
- - Metro Link Public License 1.00 (available at http://www.opengroup.org/openmotif/supporters/metrolink/license.html)
- - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)
-
-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. 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
- 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.
-
-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/TMP/org.eclipse.sdk.epp/pom.xml b/TMP/org.eclipse.sdk.epp/pom.xml
deleted file mode 100644
index 67fa93fb3..000000000
--- a/TMP/org.eclipse.sdk.epp/pom.xml
+++ /dev/null
@@ -1,73 +0,0 @@
-
-
-
-
- 4.0.0
-
-
- org.eclipse
- eclipse-parent
- 1.0.0-SNAPSHOT
- ../../eclipse-parent
-
-
- org.eclipse.sdk.epp
- 4.2.0-SNAPSHOT
- eclipse-repository
-
-
-
-
-
-
- org.eclipse.tycho
- tycho-p2-director-plugin
-
-
- materialize-products
-
- materialize-products
-
-
- SDKProfile
-
-
- org.eclipse.sdk.epp
- eclipse
-
-
-
-
-
- archive-products
-
- archive-products
-
-
-
- zip
- tar.gz
- tar.gz
-
-
-
-
-
-
-
-
-
diff --git a/TMP/rcp.config/CVS/Entries b/TMP/rcp.config/CVS/Entries
deleted file mode 100644
index 1915b9f1f..000000000
--- a/TMP/rcp.config/CVS/Entries
+++ /dev/null
@@ -1,6 +0,0 @@
-/build.properties/1.26/Tue Jun 7 13:22:45 2011//
-/buildConfiguration.xml/1.11/Fri Feb 18 21:26:47 2011//
-/config.product/1.2/Thu Apr 23 21:26:40 2009//
-/feature.properties/1.1/Tue Apr 28 15:27:27 2009//
-/feature.xml/1.3/Tue Apr 28 15:27:27 2009//
-/p2.inf/1.9/Fri May 22 20:51:28 2009//
diff --git a/TMP/rcp.config/CVS/Repository b/TMP/rcp.config/CVS/Repository
deleted file mode 100644
index 011b21b03..000000000
--- a/TMP/rcp.config/CVS/Repository
+++ /dev/null
@@ -1 +0,0 @@
-org.eclipse.releng.eclipsebuilder/eclipse/buildConfigs/rcp.config
diff --git a/TMP/rcp.config/CVS/Root b/TMP/rcp.config/CVS/Root
deleted file mode 100644
index 2d37d165b..000000000
--- a/TMP/rcp.config/CVS/Root
+++ /dev/null
@@ -1 +0,0 @@
-:pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse
diff --git a/TMP/rcp.config/build.properties b/TMP/rcp.config/build.properties
deleted file mode 100755
index acf1faa19..000000000
--- a/TMP/rcp.config/build.properties
+++ /dev/null
@@ -1,49 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2009 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-# IBM Corporation - initial API and implementation
-###############################################################################
-
-root.permissions.755=eclipse
-root.win32.win32.x86=absolute:${buildDirectory}/features/org.eclipse.equinox.executable/bin/win32/win32/x86
-root.win32.win32.x86_64=absolute:${buildDirectory}/features/org.eclipse.equinox.executable/bin/win32/win32/x86_64
-root.aix.gtk.ppc=absolute:${buildDirectory}/features/org.eclipse.equinox.executable/bin/gtk/aix/ppc
-root.aix.gtk.ppc64=absolute:${buildDirectory}/features/org.eclipse.equinox.executable/bin/gtk/aix/ppc64
-root.hpux.gtk.ia64_32=absolute:${buildDirectory}/features/org.eclipse.equinox.executable/bin/gtk/hpux/ia64_32
-root.solaris.gtk.sparc=absolute:${buildDirectory}/features/org.eclipse.equinox.executable/bin/gtk/solaris/sparc
-root.solaris.gtk.x86=absolute:${buildDirectory}/features/org.eclipse.equinox.executable/bin/gtk/solaris/x86
-
-root.linux.gtk.x86=absolute:${buildDirectory}/features/org.eclipse.platform/about_files/linux.gtk.x86,absolute:${buildDirectory}/features/org.eclipse.equinox.executable/bin/gtk/linux/x86
-root.linux.gtk.x86.permissions.755=*.so*
-root.linux.gtk.ppc64=absolute:${buildDirectory}/features/org.eclipse.platform/about_files/linux.gtk.ppc,absolute:${buildDirectory}/features/org.eclipse.equinox.executable/bin/gtk/linux/ppc64
-root.linux.gtk.ppc64.permissions.755=*.so*
-root.linux.gtk.x86_64=absolute:${buildDirectory}/features/org.eclipse.platform/about_files/linux.gtk.x86_64,absolute:${buildDirectory}/features/org.eclipse.equinox.executable/bin/gtk/linux/x86_64
-root.linux.gtk.x86_64.permissions.755=*.so*
-root.linux.gtk.s390x=absolute:${buildDirectory}/features/org.eclipse.platform/about_files/linux.gtk.s390x,absolute:${buildDirectory}/features/org.eclipse.equinox.executable/contributed/gtk/linux/s390x
-root.linux.gtk.s390x.permissions.755=*.so*
-root.linux.gtk.s390=absolute:${buildDirectory}/features/org.eclipse.platform/about_files/linux.gtk.s390,absolute:${buildDirectory}/features/org.eclipse.equinox.executable/contributed/gtk/linux/s390
-root.linux.gtk.s390.permissions.755=*.so*
-
-root.macosx.cocoa.x86.folder.Eclipse.app/Contents/MacOS=absolute:file:${buildDirectory}/features/org.eclipse.equinox.executable/bin/cocoa/macosx/x86/Eclipse.app/Contents/MacOS/eclipse
-root.macosx.cocoa.x86.folder.Eclipse.app/Contents/Resources=absolute:${buildDirectory}/features/org.eclipse.equinox.executable/bin/cocoa/macosx/x86/Eclipse.app/Contents/Resources
-root.macosx.cocoa.x86.folder.Eclipse.app/Contents=absolute:file:${buildDirectory}/features/org.eclipse.equinox.executable/bin/cocoa/macosx/x86/Eclipse.app/Contents/Info.plist
-root.macosx.cocoa.x86.permissions.755=Eclipse.app/Contents/MacOS/eclipse,Eclipse.app/Contents/MacOS/java_swt
-root.macosx.cocoa.x86.link=Eclipse.app/Contents/MacOS/eclipse,eclipse
-
-root.macosx.cocoa.x86_64.folder.Eclipse.app/Contents/MacOS=absolute:file:${buildDirectory}/features/org.eclipse.equinox.executable/bin/cocoa/macosx/x86_64/Eclipse.app/Contents/MacOS/eclipse
-root.macosx.cocoa.x86_64.folder.Eclipse.app/Contents/Resources=absolute:${buildDirectory}/features/org.eclipse.equinox.executable/bin/cocoa/macosx/x86_64/Eclipse.app/Contents/Resources
-root.macosx.cocoa.x86_64.folder.Eclipse.app/Contents=absolute:file:${buildDirectory}/features/org.eclipse.equinox.executable/bin/cocoa/macosx/x86_64/Eclipse.app/Contents/Info.plist
-root.macosx.cocoa.x86_64.permissions.755=Eclipse.app/Contents/MacOS/eclipse,Eclipse.app/Contents/MacOS/java_swt
-root.macosx.cocoa.x86_64.link=Eclipse.app/Contents/MacOS/eclipse,eclipse
-
-
-
-
-
-
-
diff --git a/TMP/rcp.config/buildConfiguration.xml b/TMP/rcp.config/buildConfiguration.xml
deleted file mode 100755
index 7ef7e9277..000000000
--- a/TMP/rcp.config/buildConfiguration.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/TMP/rcp.config/config.product b/TMP/rcp.config/config.product
deleted file mode 100755
index da4fbe94c..000000000
--- a/TMP/rcp.config/config.product
+++ /dev/null
@@ -1,5 +0,0 @@
-
-
-
-
-
diff --git a/TMP/rcp.config/feature.properties b/TMP/rcp.config/feature.properties
deleted file mode 100755
index 3f0136176..000000000
--- a/TMP/rcp.config/feature.properties
+++ /dev/null
@@ -1,24 +0,0 @@
-###############################################################################
-# Copyright (c) 2009 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-# IBM Corporation - initial API and implementation
-###############################################################################
-# feature.properties
-# contains externalized strings for feature.xml
-# "%foo" in feature.xml corresponds to the key "foo" in this file
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# This file should be translated.
-
-# "featureName" property - name of the feature
-featureName=Eclipse Product Configuration
-
-# "providerName" property - name of the company that provides the feature
-providerName=Eclipse.org
-
-# "description" property - description of the feature
-description=Configuration information for the Eclipse product
diff --git a/TMP/rcp.config/feature.xml b/TMP/rcp.config/feature.xml
deleted file mode 100755
index 98081dc63..000000000
--- a/TMP/rcp.config/feature.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
-
- %description
-
-
-
diff --git a/TMP/rcp.config/p2.inf b/TMP/rcp.config/p2.inf
deleted file mode 100755
index 118d85298..000000000
--- a/TMP/rcp.config/p2.inf
+++ /dev/null
@@ -1,9 +0,0 @@
-org.eclipse.pde.build.append.startlevels=false
-org.eclipse.pde.build.append.launchers=true
-properties.1.name=org.eclipse.equinox.p2.type.group
-properties.1.value=false
-
-instructions.configure.import=org.eclipse.equinox.p2.touchpoint.eclipse.setLauncherName
-instructions.configure=setLauncherName(name:eclipse);
-instructions.unconfigure.import=org.eclipse.equinox.p2.touchpoint.eclipse.setLauncherName
-instructions.unconfigure=setLauncherName();
diff --git a/TMP/rcp.config/pom.xml b/TMP/rcp.config/pom.xml
deleted file mode 100644
index df4fa2569..000000000
--- a/TMP/rcp.config/pom.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
- 4.0.0
-
-
- org.eclipse
- eclipse-parent
- 1.0.0-SNAPSHOT
-
-
- org.eclipse.rcp.configuration
- org.eclipse.rcp.configuration
- 1.0.0-SNAPSHOT
- eclipse-feature
-
-
diff --git a/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/eclipse-junit-tests.product b/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/eclipse-junit-tests.product
new file mode 100755
index 000000000..9f53d3d27
--- /dev/null
+++ b/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/eclipse-junit-tests.product
@@ -0,0 +1,11 @@
+
+
+
+
+
+
+
+
+
+
+
diff --git a/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/pom.xml b/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/pom.xml
new file mode 100644
index 000000000..4b3ae34a8
--- /dev/null
+++ b/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/pom.xml
@@ -0,0 +1,156 @@
+
+
+
+
+ 4.0.0
+
+
+ org.eclipse
+ eclipse-parent
+ 1.0.0-SNAPSHOT
+ ../eclipse-parent
+
+
+ eclipse-junit-tests
+ eclipse-repository
+
+
+
+
+ ${project.artifactId}
+
+
+
+ src/main/resources
+ true
+
+
+
+
+
+ org.apache.maven.plugins
+ maven-resources-plugin
+ 2.5
+
+
+ filter-resources
+
+ resources
+
+ process-resources
+
+ ${project.build.directory}/resources
+ \
+
+
+
+
+
+
+ org.eclipse.tycho
+ target-platform-configuration
+
+ p2
+
+
+ linux
+ gtk
+ x86
+
+
+ linux
+ gtk
+ x86_64
+
+
+ win32
+ win32
+ x86
+
+
+ win32
+ win32
+ x86_64
+
+
+ macosx
+ cocoa
+ x86_64
+
+
+
+
+
+ org.eclipse.tycho
+ tycho-p2-repository-plugin
+
+
+ archive-repository
+ package
+
+ archive-repository
+
+
+
+
+
+ org.eclipse.cbi
+ maven-cbi-plugin
+ 0.0.1-SNAPSHOT
+
+
+ plugin-versions
+
+ plugin-versions
+
+ package
+
+ ${project.build.directory}/resources/finalPluginsVersions.properties
+
+
+
+ test-properties
+
+ test-properties
+
+ package
+
+ ${project.build.directory}/resources/test.properties
+
+
+
+
+
+ org.apache.maven.plugins
+ maven-assembly-plugin
+
+
+ src/main/assembly/assembly.xml
+
+
+
+
+ make-assembly
+ package
+
+ single
+
+
+
+
+
+
+
+
diff --git a/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/src/main/assembly/assembly.xml b/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/src/main/assembly/assembly.xml
new file mode 100644
index 000000000..86d59c11b
--- /dev/null
+++ b/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/src/main/assembly/assembly.xml
@@ -0,0 +1,24 @@
+
+ bundle
+
+ zip
+
+ false
+
+
+ ${project.basedir}/src/main/scripts
+ /
+
+
+ ${project.build.directory}/resources
+ /
+
+
+
+
+
+ /
+ eclipse-junit-tests-${buildQualifier}.zip
+
+
+
diff --git a/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/src/main/resources/equinoxp2tests.properties b/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/src/main/resources/equinoxp2tests.properties
new file mode 100644
index 000000000..726eb2bd6
--- /dev/null
+++ b/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/src/main/resources/equinoxp2tests.properties
@@ -0,0 +1,18 @@
+#Properties required by equinox p2 tests
+#Wed, 14 Mar 2012 19:41:56 -0400
+
+org.eclipse.equinox.p2.reconciler.tests.platform.archive.linux=\${basedir}/eclipse-platform-${buildQualifier}-linux-gtk.tar.gz
+org.eclipse.equinox.p2.reconciler.tests.platform.archive.linux-x86_64=\${basedir}/eclipse-platform-${buildQualifier}-linux-gtk-x86_64.tar.gz
+org.eclipse.equinox.p2.reconciler.tests.platform.archive.win32=\${basedir}\\eclipse-platform-${buildQualifier}-win32.zip
+org.eclipse.equinox.p2.reconciler.tests.platform.archive.win32-x86_64=\${basedir}\\\\eclipse-platform-${buildQualifier}-win32-x86_64.zip
+org.eclipse.equinox.p2.reconciler.tests.platform.archive.macosx=\${basedir}/eclipse-platform-${buildQualifier}-macosx-cocoa.tar.gz
+org.eclipse.equinox.p2.reconciler.tests.platform.archive.macosx-x86_64=\${basedir}/eclipse-platform-${buildQualifier}-macosx-cocoa-x86_64.tar.gz
+org.eclipse.equinox.p2.reconciler.tests.lastrelease.platform.archive.linux=\${basedir}/eclipse-platform-3.7.2-linux-gtk.tar.gz
+org.eclipse.equinox.p2.reconciler.tests.lastrelease.platform.archive.linux-x86_64=\${basedir}/eclipse-platform-3.7.2-linux-gtk-x86_64.tar.gz
+org.eclipse.equinox.p2.reconciler.tests.lastrelease.platform.archive.win32=\${basedir}\\\\eclipse-platform-3.7.2-win32.zip
+org.eclipse.equinox.p2.reconciler.tests.lastrelease.platform.archive.win32-x86_64=\${basedir}\\\\eclipse-platform-3.7.2-win32-x86_64.zip
+org.eclipse.equinox.p2.reconciler.tests.lastrelease.platform.archive.macosx=\${basedir}/eclipse-platform-3.7.2-macosx-cocoa.tar.gz
+org.eclipse.equinox.p2.reconciler.tests.lastrelease.platform.archive.macosx-x86_64=\${basedir}/eclipse-platform-3.7.2-macosx-cocoa-x86_64.tar.gz
+org.eclipse.equinox.p2.tests.current.build.repo=file:/shared/eclipse/e4/lts/R3_platform-aggregator/TMP/org.eclipse.sdk.epp/target/repository/
+org.eclipse.equinox.p2.tests.last.release.build.repo=http://download.eclipse.org/eclipse/updates/3.7/R-3.7-201106131736
+
diff --git a/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/src/main/resources/label.properties b/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/src/main/resources/label.properties
new file mode 100644
index 000000000..81c91a842
--- /dev/null
+++ b/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/src/main/resources/label.properties
@@ -0,0 +1,5 @@
+# can't access timestamp, so use version qualifier instead
+timestamp=${buildQualifier}
+buildType=I
+buildId=${buildQualifier}
+buildLabel=${buildQualifier}
diff --git a/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/src/main/scripts/readme.html b/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/src/main/scripts/readme.html
new file mode 100755
index 000000000..d1df078e5
--- /dev/null
+++ b/eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/src/main/scripts/readme.html
@@ -0,0 +1,183 @@
+
+
+
+
+Automated Testing of Eclipse Builds
+
+
+
+ Automated Testing of Eclipse Builds
+
Last updated: March 2, 2011
Description
This document describes how to run Eclipse JUnit plugin tests from the command
+ line using Eclipse SDK JUnit test plug-ins and a testing framework. This method of running tests is intended
+ for anyone who wishes to automate their testing process or reproduce the testing
+ mechanism used in Eclipse builds by the Eclipse Platform Release Engineering team.
Click here for a description of the testing
+ framework, and how it can be used outside of the setup described here.
If you simply wish to write and run JUnit tests interactively from an Eclipse
+ workbench, try one of the links below:
All test machines will require 1.4 and 1.5 java runtime environments installed to run all tests. See test targets
+ for details on which tests require a 1.5 level jre. All other tests can be executed with either jre levels.
+
+
A properties file containing the following key-value pair: J2SE-5.0=<path to 1.5 java executable>. On Windows, the path must be enclosed with double quotes if it contains any space characters, e.g. J2SE-5.0="c:/program files/jdk1.5.0/jre/bin/java".
+
+
Info-ZIP UnZip version 5.41 or later installed and added to the path.
+
+
The JUnit Plugin Tests eclipse-Automated-Tests-<buildId>.zip from an Eclipse build (http://download.eclipse.org/eclipse/downloads/).
+ This ZIP contains this document, scripts to run the tests, the test framework plug-ins and the JUnit test plug-ins.
+
+
An Eclipse SDK distribution (http://download.eclipse.org/eclipse/downloads/)
+ to test. Usually you will want to test a particular Eclipse build using a matching
+ Automated Tests feature.
+
+
To run the pde build tests you will need the eclipse-<buildId>delta-pack.zip.
+
+
To run the Team CVS tests you will need extssh access to a CVS repository.
+ The tests create a lot of junk modules and tags so you will want to keep the
+ test repository seperate from your development repository. While it is not necessary
+ to clean up the repository between each Team test run you will probably want
+ to clean it up periodically.
+
+
Some of the p2 tests require a copy of the Eclipse Platform Runtime Binary archive for the platform you
+ are testing. More information is available from the Equinox Testing Wiki page.
+
+
+
Setup
+
+
Extract the eclipse-Automated-Tests-<buildId>.zip or tar.gz. On Window, extract this file close to the root of the drive to prevent some path names from exceeding
+ the 255 character limit. This will create a top-level directory eclipse-testing.
+
+
Place the Eclipse SDK distribution to test (and the Eclipse Platform Runtime Binary) in the eclipse-testing directory.
+ Do not extract these files as the test scripts will take care of this.
+
To run the Team CVS tests, edit the test.xml script to provide connection
+ information. Replace the following strings in the teamcvs target of the test.xml file with the information described below:
+
+
@cvs_user@ - the account used to connect to the cvs repository
+
@cvs_password@ - the account password
@cvs_host@- the name of the cvs server
+
@cvs_root@ - the repository path
+
+ These values are used at test time to automatically replace strings in
+ org.eclipse.team.tests.cvs.core/repository.properties. For more information
+ on how this file is used in the team CVS tests, click here.
+
+
+
To Run the PDE build scripts, save the eclipse-<buildId>delta-pack.zip to the eclipse-testing directory.
All parameters and targets are optional on windows systems with the exception of "-properties". On *nix systems, the os, ws and arch parameters
+ must be specified in addition to the -properties parameter.
The JUnit test results are produced in individual xml files for each test plug-in with a test.xml. These
+ results are copied to the eclipse-testing\results\xml directory. These results
+ can be converted into html by running the "genHtml" target as described
+ in the table below. Please be aware that "Build Successful" printed
+ to the console is NOT indicative of tests passing.
+
+
+
Parameters
+
+
Parameter
Description
+
+
-os <operating system>
The OS the tests are being run on. One of: aix, hpux, linux, macosx, solaris,
+ win32. Default win32
+
+
-ws <windowing system>
The windowing system the tests are being run on. One of: cocoa, gtk, photon,
+ win32. Default win32
+
+
-arch <architecture>
The architecture the tests are being run on. One of: ppc, PA_RISC, x86,
+ sparc. Default x86
+
+
-noclean
Run tests without installing a clean Eclipse (in "test-eclipse") between test targets. Default
+ is to delete an existing test-eclipse directory and re-extract the Eclipse distribution between test targets.
+
+
-properties
As per requirements noted above, this is used to reference a properties file containing additional Ant properties
+ used in running tests.Can be used to pass additional vm arguments to the
+ Java virtual machine running the tests by adding the entry "extraVMargs=<the
+ args to pass to the vm>" to the specified properties file.
At a minimum, the property file must include a "J2SE-5.0" property which specifies a path to a 1.5 java executable, for example:
The path must be enclosed in double quotes if it contains spaces. This key-value pair is required to run JUnit plug-in tests that require a 1.5 level jvm.
+
+
-vm
When runtests is executed, two instances of eclipse are started: one to invoke the org.eclipse.ant.core.antRunner application to run a test.xml script in a test plug-in (outer instance) and another in which the JUnit tests are being executed (inner). By default, both will use the java executable on the system path. The -vm property is used to specify an alternate java executable.
+ For example, "-vm c:\jdk142\jre\bin\java".
However, the -vm value is ignored by the inner vm for JUnit plug-in tests requiring a 1.5 JRE to execute (see test targets). This property must be used in conjunction with the -properties parameter described above at all times.
+
+
-Dtest.target=performance
Runs the performance target only in each test plug-in's test.xml. When running tests on Windows,
+ enclose this parameter in double quotes, ie. runtests "-Dtest.target=performance".
targetname1 targetname2 targetname3 etc..
Replace with a list of test targets to execute (space delineated). Each corresponds to an Ant target in the eclipse-testing/test.xml script.
For example, runtests -os linux -ws gtk -arch x86 ant antui -properties vm.properties This will execute the "ant" and "antui" test targets only. If not specified, the "all" target will be executed.
+
Appendix A - Test Targets
Ant targets in the main test.xml which execute tests. Typically each corresponds
+ to the execution of a test plug-in's test.xml.
Target name (special jvm requirements)
Description / test plug-in
+
+
all (1.4, 1.5 and 1.6 JREs required)
Runs all the targets below. Default.
+
ant
org.eclipse.ant.tests.core
+
antui
org.eclipse.ant.tests.ui
+
compare
org.eclipse.compare.tests
+
coreexpressions
org.eclipse.core.expressions.tests
+
coreresources
org.eclipse.core.tests.resources
+
coreruntime
org.eclipse.core.tests.runtime
+
coretestsnet
org.eclipse.core.tests.net
+
equinoxsecurity
org.eclipse.equinox.security.tests
+
filebuffers
org.eclipse.core.filebuffers.tests
+
jdtapt (JRE 1.5 required)
org.eclipse.jdt.apt.tests
+
jdtaptpluggable (JRE 1.6 required)
org.eclipse.jdt.apt.pluggable.tests
+
jdtcompilerapt (JRE 1.6 required)
org.eclipse.jdt.compiler.apt.tests
+
jdtcompilertool (JRE 1.6 required)
org.eclipse.jdt.compiler.tool.tests
+
jdtcorebuilder (JRE 1.5 required)
org.eclipse.jdt.core.tests.builder
+
jdtcorecompiler (JRE 1.5 required)
org.eclipse.jdt.core.tests.compiler
+
jdtcoremodel (JRE 1.5 required)
org.eclipse.jdt.core.tests.model
+
jdtcoreperf
org.eclipse.jdt.core.tests.performance
+
jdtdebug
org.eclipse.jdt.debug.tests
+
jdttext
org.eclipse.jdt.text.tests
+
jdtui
org.eclipse.jdt.ui.tests
+
jdtuirefactoring
org.eclipse.jdt.ui.tests.refactoring
+
jface
org.eclipse.jface.text.tests
+
jfacedatabinding
org.eclipse.jface.tests.databinding
+
ltkcorerefactoringtests
org.eclipse.ltk.core.refactoring.tests
+
ltkuirefactoringtests
org.eclipse.ltk.ui.refactoring.tests
+
osgi
org.eclipse.osgi.tests
+
pdeapitooling (JRE 1.5 required)
org.eclipse.pde.api.tools.tests
+
pdebuild
org.eclipse.pde.build.tests
+
pdeui
org.eclipse.pde.ui.tests
+
relEng
org.eclipse.releng.tests
+
swt
org.eclipse.swt.tests
+
teamcore
org.eclipse.team.tests.core
+
teamcvs
org.eclipse.team.tests.cvs.core
+
text
org.eclipse.text.tests
+
ua
org.eclipse.ua.tests
+
ui
org.eclipse.ui.tests
+
uieditors
org.eclipse.ui.editors.tests
+
uiforms
org.eclipse.ui.tests.forms
+
uinavigator
org.eclipse.ui.tests.navigator
+
uiperformance
org.eclipse.ui.tests.performance
+
uircp
org.eclipse.ui.tests.rcp
+
uiviews
org.eclipse.ui.tests.views.properties.tabbed
+
uiworkbenchtexteditor
org.eclipse.ui.workbench.texteditor.tests
+
update
org.eclipse.update.tests.core
+
+
+
+
Appendix B - Supported os, ws, and arch
+ value combinations
The following table contains the values that can be used with the -os, -ws,
+ and -arch switches.