Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat (limited to 'production/testScripts/configuration/sdk.tests/testScripts/test.xml')
-rw-r--r--production/testScripts/configuration/sdk.tests/testScripts/test.xml310
1 files changed, 157 insertions, 153 deletions
diff --git a/production/testScripts/configuration/sdk.tests/testScripts/test.xml b/production/testScripts/configuration/sdk.tests/testScripts/test.xml
index 62ecdf2d..d93c0791 100644
--- a/production/testScripts/configuration/sdk.tests/testScripts/test.xml
+++ b/production/testScripts/configuration/sdk.tests/testScripts/test.xml
@@ -5,7 +5,7 @@
basedir=".">
- <!--Directory name of org.eclipse.test plug-in installed in ${eclipse-home}-->
+ <!--Directory name of org.eclipse.test plug-in installed in ${eclipse-home} -->
<target
name="setup"
unless="noclean"
@@ -25,11 +25,11 @@
substring=".tar.gz" />
</condition>
<!--
- <condition
+ <condition
property="repoexists"
value="true">
<available file="${repoLocation}" />
- </condition>
+ </condition>
-->
<condition
property="extraIU"
@@ -113,7 +113,7 @@
value="true" />
</target>
- <!--setup for zip archives-->
+ <!--setup for zip archives -->
<target
name="setup-zip"
depends="init"
@@ -137,7 +137,7 @@
</target>
- <!--setup for tar.gz archives-->
+ <!--setup for tar.gz archives -->
<target
name="setup-tar.gz"
depends="init"
@@ -152,7 +152,7 @@
<delete
dir="${eclipse-home}"
verbose="false" />
-
+
<echo message="Fresh extract ${runtimeArchive} into ${install} for testing." />
<exec
dir="${install}"
@@ -170,7 +170,7 @@
<!--
we now write this file, just for p2 tests, instead of doing
the funky ant replace
- <loadproperties srcfile="equinoxp2tests.properties" />
+ <loadproperties srcfile="equinoxp2tests.properties" />
-->
<condition
property="platformArchive"
@@ -207,7 +207,7 @@
<os family="mac" />
<os family="unix" />
<!-- should not need, as long as x86_64 rules (above) comes first
- <os arch="i386" />
+ <os arch="i386" />
-->
</and>
</condition>
@@ -267,17 +267,17 @@
message="platformTarget is not defined. Check that platformArchive variable and value is defined correctly, such as in equinoxp2tests.properties in the appropriate testConfig" />
<echo message="platformTarget ${platformTarget} platformArchive ${platformArchive}" />
<!-- The "platformArchive" is a minimal, stable vesion of eclipse runtime binary,
- that is used only for its "p2Director" application, to install tests into
- to target test environment. The intent is to make sure that apart of the tests
- works consistently, and does not "break the tests", simply because of some recent
- but in p2Director. (while unlikely, these days ... since that code is not under active
- development ... you never know)
- -->
+ that is used only for its "p2Director" application, to install tests into
+ to target test environment. The intent is to make sure that apart of the tests
+ works consistently, and does not "break the tests", simply because of some recent
+ but in p2Director. (while unlikely, these days ... since that code is not under active
+ development ... you never know)
+ -->
<antcall target="${platformTarget}" />
</target>
- <!--setup for platform zip archives-->
+ <!--setup for platform zip archives -->
<target
name="platform-zip"
depends="init"
@@ -299,7 +299,7 @@
</exec>
</target>
- <!--setup for platform tar.gz archives-->
+ <!--setup for platform tar.gz archives -->
<target
name="platform-tar.gz"
depends="init"
@@ -432,16 +432,16 @@
<arg line="-bundlepool ${eclipse-home}" />
</java>
<!--
- <exec
+ <exec
dir="."
executable="unzip">
<arg line="-o eclipse-junit-tests-*.zip ${derby} -d ${install}" />
- </exec>
- <copy todir="${install}/eclipse/dropins/eclipse/plugins">
+ </exec>
+ <copy todir="${install}/eclipse/dropins/eclipse/plugins">
<fileset
- dir="${repoLocation}/eclipse/dropins/eclipse/plugins"
- includes="org.apache.derby**/*" />
- </copy>
+ dir="${repoLocation}/eclipse/dropins/eclipse/plugins"
+ includes="org.apache.derby**/*" />
+ </copy>
-->
</target>
@@ -460,9 +460,9 @@
name="initProductionProperties"
depends="initWorkspace">
<!--
- during production testing, previous steps persists some properties
- that we would otherwise not have access too. Such as those set on
- Hudson command line.
+ during production testing, previous steps persists some properties
+ that we would otherwise not have access too. Such as those set on
+ Hudson command line.
-->
<property file="${WORKSPACE}/production.properties" />
@@ -485,10 +485,10 @@
<fail
unless="buildId"
message="buildId value must be provided by caller (such as 'I20120717-0800'" />
- <!--
- this "buildId check" may be overly strict, but best to start off strict for now,
- loosen in future if we start to find/have variety
- -->
+ <!--
+ this "buildId check" may be overly strict, but best to start off strict for now,
+ loosen in future if we start to find/have variety
+ -->
<condition property="buildIdOK">
<matches
pattern="^[IMXYNPSR]\d{8}-\d{4}$"
@@ -513,9 +513,9 @@
</target>
<!--
- main purpose of initStreamVariables, it to be sure we have eclipseStreamMajor and eclipseStreamMinor
- Uses script, which requires Java 1.6 (or ... else gets complicated to setup)
- -->
+ main purpose of initStreamVariables, it to be sure we have eclipseStreamMajor and eclipseStreamMinor
+ Uses script, which requires Java 1.6 (or ... else gets complicated to setup)
+ -->
<target
name="initStreamVariables"
depends="initDownloadHosts">
@@ -525,11 +525,11 @@
unless="eclipseStream"
message="eclipseStream value must be provided by caller, such as '4.3.0'." />
<!--
- Not clear why, but I've seen "eclipseStream" value have a trailing
- ?blank? that gets picked up when read in as string.
- Seems it might be a couple of ant issues?
- Luckily we never use it as a whole string (just major and minor)
- so we can ignore spaces.
+ Not clear why, but I've seen "eclipseStream" value have a trailing
+ ?blank? that gets picked up when read in as string.
+ Seems it might be a couple of ant issues?
+ Luckily we never use it as a whole string (just major and minor)
+ so we can ignore spaces.
-->
<condition property="streamOK">
<matches
@@ -564,7 +564,7 @@
unless="eclipseStreamMinor"
message="eclipseStreamMinor not defined or computable" />
<!--
- <fail
+ <fail
unless="eclipseStreamService"
message="eclipseStreamService not defined or computable" />
-->
@@ -589,7 +589,7 @@
<echo message="executionDir: ${executionDir}" />
- <!--default directory where test-eclipse-sdk will be installed-->
+ <!--default directory where test-eclipse-sdk will be installed -->
<property
name="install"
value="${executionDir}/test-eclipse" />
@@ -625,7 +625,7 @@
<mkdir dir="${platformLocation}" />
<echo message="platformLocation: ${platformLocation}" />
- <!-- The directory that will contain all files containing information on the tests that ran.-->
+ <!-- The directory that will contain all files containing information on the tests that ran. -->
<property
name="results"
value="${executionDir}/results" />
@@ -635,7 +635,7 @@
<echo message="results: ${results}" />
<!--Directory for JUnit report output, console log output and .log content for each test suite.
- Overrides default in org.eclipse.test/library.xml-->
+ Overrides default in org.eclipse.test/library.xml -->
<property
name="junit-report-output"
value="${results}/${testedPlatform}" />
@@ -671,8 +671,8 @@
</target>
<!--
- DOWNLOAD_HOST and ARCHIVE_HOST can be defined on command line,
- if running on local test environments.
+ DOWNLOAD_HOST and ARCHIVE_HOST can be defined on command line,
+ if running on local test environments.
-->
<target
name="initDownloadHosts"
@@ -703,10 +703,10 @@
<property environment="env" />
<!--
- Normally these files are copied by other scripts, if not simply testing this script with "testTestXMLScript.sh",
- but when testing in isolation, want this simple way to
- copy what we need. Note: the testCopyFileIfTesting target
- will need adjustment, depending on OS that the testing is done on.
+ Normally these files are copied by other scripts, if not simply testing this script with "testTestXMLScript.sh",
+ but when testing in isolation, want this simple way to
+ copy what we need. Note: the testCopyFileIfTesting target
+ will need adjustment, depending on OS that the testing is done on.
-->
<antcall target="testCopyFilesIfTesting" />
@@ -731,29 +731,29 @@
Try using "loadproperties", instead of "properties file=" to see if
that will "evaluate" variables as loaded. Otherwise, the <properties form
has to move to "top of file" ... outer scope?
- <property file="${eclipseBuilderDir}/eclipse/buildConfigs/sdk.tests/testConfigs/${testPlatform}/testing.properties" />
+ <property file="${eclipseBuilderDir}/eclipse/buildConfigs/sdk.tests/testConfigs/${testPlatform}/testing.properties" />
- <property
+ <property
name="testingPropertiesfile"
value="${executionDir}/testing.properties" />
- <loadproperties>
+ <loadproperties>
<file file="${testingPropertiesfile}" />
- </loadproperties>
--->
+ </loadproperties>
+ -->
<!--
- suffix added to test output files, along with VM number,
- to identify platform on which tests ran. (currently
- hard coded in vm.properties)
+ suffix added to test output files, along with VM number,
+ to identify platform on which tests ran. (currently
+ hard coded in vm.properties)
-->
<!-- <property file="vm.properties" /> -->
<!--now set in initBasicDirectories
- <property
+ <property
name="testedPlatform"
value="${os}.${ws}.${arch}" />
--->
+ -->
<!--Unlock files on the Mac before starting tests.
- Required to delete some workspace directories (org.eclipse.core.filebuffers.tests and Team CVS tests).-->
+ Required to delete some workspace directories (org.eclipse.core.filebuffers.tests and Team CVS tests). -->
<exec
dir="${executionDir}"
executable="chflags"
@@ -762,11 +762,11 @@
</exec>
<!--
- Originally needed/provided for p2 tests, but they appear not to
- be successful in reading or using these proerties any longer.
- Not clear why. So we'll leave it in until understood. (It may be
- useful in other scenarios, such when tested stand alone?)
- -->
+ Originally needed/provided for p2 tests, but they appear not to
+ be successful in reading or using these proerties any longer.
+ Not clear why. So we'll leave it in until understood. (It may be
+ useful in other scenarios, such when tested stand alone?)
+ -->
<property
name="org.eclipse.equinox.p2.reconciler.tests.platform.archive"
value="${executionDir}/${platformArchive}" />
@@ -785,8 +785,8 @@
value="${last.release.build.repo}" />
<!--
- It is likely we do not need the equinoxp2propertiesFile any longer,
- during production tests, at least.
+ It is likely we do not need the equinoxp2propertiesFile any longer,
+ during production tests, at least.
-->
<antcall target="rewriteEquinoxp2PropertiesFile" />
@@ -825,14 +825,14 @@
</target>
<!-- runtimeArchive is set to either current, just built SDK, or
- if "baselinePerf" has been set to true, then that baselinePerf version is used,
- such as for performance baselinePerf run. baselinePerf is set in Hudson
- job.
+ if "baselinePerf" has been set to true, then that baselinePerf version is used,
+ such as for performance baselinePerf run. baselinePerf is set in Hudson
+ job.
-->
<target
name="setRuntimeArchive"
unless="runtimeArchive">
- <!-- we'll check "alt" baselinePerf first. This is what's used for "several releases ago", or similar. -->
+ <!-- we'll check "alt" baselinePerf first. This is what's used for "several releases ago", or similar. -->
<condition
property="buildIdToUse"
value="${baselinePerfAltVersionLabel}">
@@ -1068,8 +1068,8 @@
value="VM used for tests, is same that invoked Ant: '${java.home}/bin/java' (that is, 'jvm' not specified by caller)." />
<echo message="VMSource: $VMSource" />
<!--
- Remember, we don't want J2SE-X.0 set at all, if there is nothing
- that can run tests that require that level.
+ Remember, we don't want J2SE-X.0 set at all, if there is nothing
+ that can run tests that require that level.
-->
<exec
@@ -1080,7 +1080,7 @@
<echo message="full output from 'java -version' of ${java.home}/bin/java is " />
<echo message="${javaversion}" />
- <!--enable tests requiring 1.5 or or greater vms to run if running vm level detected matches required execution environment-->
+ <!--enable tests requiring 1.5 or or greater vms to run if running vm level detected matches required execution environment -->
<condition
property="J2SE-5.0"
value="${java.home}/bin/java">
@@ -1135,8 +1135,8 @@
value="VM used for tests, specified by caller: 'jvm'=${jvm}" />
<echo message="VMSource: $VMSource" />
<!--
- Remember, we don't want J2SE-X.0 set at all, if there is nothing
- that can run tests that require that level.
+ Remember, we don't want J2SE-X.0 set at all, if there is nothing
+ that can run tests that require that level.
-->
<exec
executable="${jvm}"
@@ -1194,10 +1194,10 @@
if="cvsPropertiesAvailable"
depends="checkCVSPropExists">
<!--
- TODO: cvstest.properties (file location) is currently
- hard coded in 'runTest2.xml' adn passed along this 'test.xml'
- via production.properties. Would be better to have the file location
- be part of the platform specific properties files, as we do with "jvm"
+ TODO: cvstest.properties (file location) is currently
+ hard coded in 'runTest2.xml' adn passed along this 'test.xml'
+ via production.properties. Would be better to have the file location
+ be part of the platform specific properties files, as we do with "jvm"
-->
<echo message="cvstest.properties file: ${cvstest.properties}" />
<property file="${cvstest.properties}" />
@@ -1251,12 +1251,12 @@
name="message"
value="start @{testPlugin}" />
</antcall>
- <!--alwasy use eclipse executable to launch tests with the exception of performance tests-->
+ <!--alwasy use eclipse executable to launch tests with the exception of performance tests -->
<!--condition property="useEclipseExe" value="true">
- <not>
- <equals arg1="${test.target}" arg2="performance"/>
- </not>
- </condition-->
+ <not>
+ <equals arg1="${test.target}" arg2="performance"/>
+ </not>
+ </condition -->
<condition
property="performance.target.present"
@@ -1264,7 +1264,7 @@
<isset property="@{testPlugin}.has.performance.target" />
</condition>
- <!--override the value of this property with performance if the tests run on performance machine-->
+ <!--override the value of this property with performance if the tests run on performance machine -->
<property
name="test.target"
value="junit" />
@@ -1274,7 +1274,7 @@
<echo message="test.target in 'runTests': ${test.target}" />
- <!--install db plug-ins if running performance tests-->
+ <!--install db plug-ins if running performance tests -->
<condition
property="derby"
value="org.apache.derby.core.feature.feature.group">
@@ -1282,8 +1282,8 @@
arg1="${test.target}"
arg2="performance" />
</condition>
- <!-- <property name="derby" value="" /> -->
- <!-- <param name="testPlugin" value="${@{testPlugin}}" /> -->
+ <!-- <property name="derby" value="" /> -->
+ <!-- <param name="testPlugin" value="${@{testPlugin}}" /> -->
<antcall target="${test.target}">
<param
name="testPlugin"
@@ -1354,18 +1354,20 @@
name="junit-stylesheet"
value="${executionDir}/JUNIT.XSL" />
<!--
- TODO: seems these "performance values" should "get into" library.xml in an easier way, that didn't require a change in library.xml.
- TODO: some question on how "fine" to make name. Such as, should "platform, architecture, window system" be "separated" from "VM value"?
- TODO: for local, non-production tests, eclipse.perf.dbloc is not being assigned value from "localTestsProperties.shsource" as it should. Perhaps needs tweak in Hudson job?
- TODO: would have to compute these in runTest2.xml, to make part of production properties,
- and phpproperties.php
+ TODO: seems these "performance values" should "get into" library.xml in an easier way, that didn't require a change in library.xml.
+ TODO: some question on how "fine" to make name. Such as, should "platform, architecture, window system" be "separated" from "VM
+ value"?
+ TODO: for local, non-production tests, eclipse.perf.dbloc is not being assigned value from "localTestsProperties.shsource" as it
+ should. Perhaps needs tweak in Hudson job?
+ TODO: would have to compute these in runTest2.xml, to make part of production properties,
+ and phpproperties.php
-->
<property
name="eclipse.perf.dbloc"
value="${eclipse.perf.dbloc.value}" />
<!-- buildIdToUse equals either baselinePerfVersion or else equalus buildId. In either case we want to collect the data -->
<!-- TODO: Do we need "buildID" coded somewhere, to know WHICH build to match with?
- Or, else will take large number of "baselines" averaged? -->
+ Or, else will take large number of "baselines" averaged? -->
<condition
property="eclipse.perf.config"
value="build=${baselinePerfAltVersion};config=${testedPlatformConfig};jvm=${javaMajorVersion}">
@@ -1378,11 +1380,13 @@
<istrue value="${baselinePerf}" />
</condition>
<!--
- This "assert" property works, in this context, because we run baseline first,
- when buildIdToUse != buildId that is a "baseline run" (so, no "assert" for that baseline run).
- But, when buildIdToUse == buildId that is a "normal run" so then we do want to "assert" against the already-collected baseline data.
- Note: Note, docs say order does not matter, and could specify "just build" and reset filled in with what's in 'config', but some experiences makes me doubt that?
- TODO: design problem: how to distinguish assert against baseline vs. baseline alt.
+ This "assert" property works, in this context, because we run baseline first,
+ when buildIdToUse != buildId that is a "baseline run" (so, no "assert" for that baseline run).
+ But, when buildIdToUse == buildId that is a "normal run" so then we do want to "assert" against the already-collected baseline
+ data.
+ Note: Note, docs say order does not matter, and could specify "just build" and reset filled in with what's in 'config', but some
+ experiences makes me doubt that?
+ TODO: design problem: how to distinguish assert against baseline vs. baseline alt.
-->
<condition
property="eclipse.perf.assertAgainst"
@@ -1617,7 +1621,7 @@
<property
name="jvm"
value="${J2SE-5.0}" />
- <!--only run test if J2SE-5.0 property set-->
+ <!--only run test if J2SE-5.0 property set -->
<condition property="skip.test">
<not>
<isset property="J2SE-5.0" />
@@ -1632,7 +1636,7 @@
<property
name="jvm"
value="${J2SE-6.0}" />
- <!--only run test if J2SE-5.0 property set-->
+ <!--only run test if J2SE-5.0 property set -->
<condition property="skip.test">
<not>
<or>
@@ -1649,7 +1653,7 @@
<target
name="jdtcorebuilder"
depends="init, setJVMProperties">
- <!--Run with 1.5 vm if it is available-->
+ <!--Run with 1.5 vm if it is available -->
<condition
property="jvm"
value="${J2SE-5.0}">
@@ -1664,7 +1668,7 @@
<property
name="jvm"
value="${J2SE-6.0}" />
- <!--only run test if J2SE-6.0 property or greater is set-->
+ <!--only run test if J2SE-6.0 property or greater is set -->
<condition property="skip.test">
<not>
<or>
@@ -1683,7 +1687,7 @@
<property
name="jvm"
value="${J2SE-6.0}" />
- <!--only run test if J2SE-6.0 property or greater is set-->
+ <!--only run test if J2SE-6.0 property or greater is set -->
<condition property="skip.test">
<not>
<or>
@@ -1827,7 +1831,7 @@
<property
name="jvm"
value="${J2SE-5.0}" />
- <!--only run test if J2SE-5.0 property set-->
+ <!--only run test if J2SE-5.0 property set -->
<condition property="skip.test">
<not>
<isset property="J2SE-5.0" />
@@ -1921,8 +1925,8 @@
name="all"
depends="init">
<!--
- <antcall target="relEng" />
- <antcall target="equinoxp2" />
+ <antcall target="relEng" />
+ <antcall target="equinoxp2" />
-->
<antcall target="quickTests" />
<antcall target="longRunningTests" />
@@ -1930,25 +1934,25 @@
</target>
<!-- This and all the performance specific targets
- are temporary, just to help investigate which work, which
- don't, etc. -->
+ are temporary, just to help investigate which work, which
+ don't, etc. -->
<target
name="allPerformance"
depends="init">
-<!-- There are 41 test suites to claim they have
- performanc targts. These "sub groups" are just
- and attempt to help investigate which work, which don't, etc. -->
+ <!-- There are 41 test suites to claim they have
+ performanc targts. These "sub groups" are just
+ and attempt to help investigate which work, which don't, etc. -->
<antcall target="selectPerformance" />
<antcall target="otherPerformance" />
</target>
<!-- This and all the performance specific targets
- are temporary, just to help investigate which work, which
- don't, etc. Visually inspected each, and found these 21 do
- have performance targets, which means there's about 20 that
- have empty peformance targets.
- -->
+ are temporary, just to help investigate which work, which
+ don't, etc. Visually inspected each, and found these 21 do
+ have performance targets, which means there's about 20 that
+ have empty peformance targets.
+ -->
<target
name="selectPerformance"
depends="init">
@@ -1959,7 +1963,7 @@
<antcall target="jdtdebug" />
<antcall target="jdtui" />
<!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=443233
- <antcall target="osgi" />
+ <antcall target="osgi" />
-->
<antcall target="pdeui" />
<antcall target="swt" />
@@ -1968,7 +1972,7 @@
<antcall target="uiforms" />
<antcall target="uiperformance" />
<!-- temp remove, we do not run these in unit tests? See bug 380553.
- <antcall target="uircp" />
+ <antcall target="uircp" />
-->
</target>
@@ -1976,13 +1980,13 @@
name="otherPerformance"
depends="init">
<!-- There is no performance tests for org.eclipse.equinox.p2.tests.ui
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=455137
- It has an empty performance target.
- <antcall target="equinoxp2ui" />
+ https://bugs.eclipse.org/bugs/show_bug.cgi?id=455137
+ It has an empty performance target.
+ <antcall target="equinoxp2ui" />
-->
<!-- Caution: org.eclipse.pde.api.tools.tests sets -Xmx to 300M, but does not set -Xms,
- so 300M might be less than -Xms
- Will "fix" on testing side, for now, by removing parameters from Hudson's scripts.
+ so 300M might be less than -Xms
+ Will "fix" on testing side, for now, by removing parameters from Hudson's scripts.
-->
<antcall target="pdeapitooling" />
<!-- These three ran but took longer an an hour, some memory issues with one of them? -->
@@ -2099,10 +2103,10 @@
</target>
<!--
- admittedly, not quite all of 'platform', but for
- now serves dual purpose of a "short set" of tests, that area
- relatively quick, and realtively reliable on build.eclipse.org hardware
- -->
+ admittedly, not quite all of 'platform', but for
+ now serves dual purpose of a "short set" of tests, that area
+ relatively quick, and realtively reliable on build.eclipse.org hardware
+ -->
<target
name="platform"
depends="init">
@@ -2146,7 +2150,7 @@
</target>
<!-- this group is "platform tests" that are Long Running
- (or, perhaps hang?, during performance tests.
+ (or, perhaps hang?, during performance tests.
-->
<target
name="platformLR"
@@ -2160,11 +2164,11 @@
<antcall target="uiperformance" />
<!-- don't run now, for 4.2. See bug 380553.
- <antcall target="uircp" />
- -->
- <!-- disable for now, bug 398717
+ <antcall target="uircp" />
+ -->
+ <!-- disable for now, bug 398717
antcall target="uiviews" /
- -->
+ -->
</target>
<target
@@ -2220,9 +2224,9 @@
<attribute name="msg" />
<sequential>
<!--
- we write the message first, with no ${line.separator} so that the timestamp can
- go on same line, and my side-effect writes an EOL
- -->
+ we write the message first, with no ${line.separator} so that the timestamp can
+ go on same line, and my side-effect writes an EOL
+ -->
<echo
message="@{msg} "
append="true"
@@ -2250,24 +2254,24 @@
<!--
- function to centralize how we get (that is, set) the value of
- 'javaMajorVersion'. (expected to be integter, such as 5,6,7,8,9,
- or will be "0" if the version could not be determined, for some reason.
+ function to centralize how we get (that is, set) the value of
+ 'javaMajorVersion'. (expected to be integter, such as 5,6,7,8,9,
+ or will be "0" if the version could not be determined, for some reason.
-->
<target name="getJavaMajorVersion">
- <!--
- TODO: this assumes we are running ant, with same VM as we'll eventuall use
- during test. Valid assumption most the time, but ... not necessarily always.
- -->
+ <!--
+ TODO: this assumes we are running ant, with same VM as we'll eventuall use
+ during test. Valid assumption most the time, but ... not necessarily always.
+ -->
<script language="javascript">
- <!--
- technically does not have to be wrapped in "CDATA" (Ant and BSD define
- it that way, but if not done, other tools (such as XML Editor) can
- break the code by changing the formatting.
- -->
+ <!--
+ technically does not have to be wrapped in "CDATA" (Ant and BSD define
+ it that way, but if not done, other tools (such as XML Editor) can
+ break the code by changing the formatting.
+ -->
<![CDATA[
var javaVersion = project.getProperty("java.version");
var pattern = new
@@ -2306,12 +2310,12 @@
</target>
<!--
- initOSes is to make sure the values of os, ws, and arch are set.
- We need them to match their "osgi.X" counterparts, so users often will
- need to simply set the "osgi.X" values as system variables, since
- our ability to guess varies from OS to OS and VM to VM ... but, if
- the osgi.X values are not set, we'll take a guess based on common systems.
- -->
+ initOSes is to make sure the values of os, ws, and arch are set.
+ We need them to match their "osgi.X" counterparts, so users often will
+ need to simply set the "osgi.X" values as system variables, since
+ our ability to guess varies from OS to OS and VM to VM ... but, if
+ the osgi.X values are not set, we'll take a guess based on common systems.
+ -->
<target name="initOSes">
<condition

Back to the top