Author: stephenc
Date: Mon Jun 27 12:51:21 2011
New Revision: 1140142
URL: http://svn.apache.org/viewvc?rev=1140142&view=rev
Log:
syncing the docs between surefire and failsafe to see what the exact
differences should be
Added:
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/configuring-classpath.apt.vm
(contents, props changed)
- copied, changed from r1140122,
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/additional-classpath.apt.vm
Removed:
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/additional-classpath.apt.vm
Modified:
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/class-loading.apt.vm
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/debugging.apt
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/inclusion-exclusion.apt.vm
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/single-test.apt
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/skipping-test.apt.vm
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/system-properties.apt.vm
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/testng.apt.vm
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/index.apt
maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/class-loading.apt.vm
Modified:
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/class-loading.apt.vm
URL:
http://svn.apache.org/viewvc/maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/class-loading.apt.vm?rev=1140142&r1=1140141&r2=1140142&view=diff
==============================================================================
---
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/class-loading.apt.vm
(original)
+++
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/class-loading.apt.vm
Mon Jun 27 12:51:21 2011
@@ -3,7 +3,7 @@
------
Dan Fabulich
------
- May 2008
+ 2010-01-09
------
~~ Licensed to the Apache Software Foundation (ASF) under one
@@ -34,7 +34,7 @@ Classloading and Forking in Maven Surefi
* Executive Summary
- If you're having problems, you'll probably want to tinker with these three
settings: forkMode, useSystemClassLoader, and useManifestOnlyJar.
+ If you're having problems, you'll probably want to tinker with these three
settings: <<<forkMode>>>, <<<useSystemClassLoader>>>, and
<<<useManifestOnlyJar>>>.
* What problem does Surefire solve?
@@ -57,7 +57,7 @@ most of the length-related problems in t
* How do people solve this problem in general?
- There are two "tricks" you can use to workaround this problem; both of them
are can cause other problems in some cases.
+ There are two "tricks" you can use to workaround this problem; both of them
can cause other problems in some cases.
1. <<Isolated Classloader>>: One workaround is to use an isolated classloader.
Instead of launching MyApp directly, we can launch some other app (a "booter")
@@ -68,18 +68,18 @@ most of the length-related problems in t
The problem with using an isolated classloader is that your classpath isn't
<really> correct, and some apps can detect this and object. For example, the
- system property "java.class.path" won't include your jars; if your app notices
+ system property <<<java.class.path>>> won't include your jars; if your app
notices
this, it could cause a problem.
There's another similar problem with using an isolated classloader: any class
- may call the static method ClassLoader.getSystemClassLoader() and attempt to
+ may call the static method <<<ClassLoader.getSystemClassLoader()>>> and
attempt to
load classes out of that classloader, instead of using the default
classloader.
- Classes often do this if they need to create classloaders of their own....
+ Classes often do this if they need to create classloaders of their own.
Unfortunately, Java-based web application servers like Jetty, Tomcat, BEA
WebLogic and IBM WebSphere are very likely to try to escape the confines of an
isolated classloader.
- 2. <<Manifest-Only Jar>>: Another workaround is to use a "manifest-only jar."
In
+ 2. <<Manifest-Only JAR>>: Another workaround is to use a "manifest-only jar."
In
this case, you create a temporary jar that's almost completely empty, except
for
a META-INF/MANIFEST.MF file. Java manifests can contain attributes that the
Java
VM will honor as directives; for example, you can have a "Class-Path"
attribute,
@@ -94,10 +94,10 @@ java -classpath booter.jar MyApp
thread context classloader and the default classloader are all the same;
there's
no possibility of "escaping" the classloader. But this is still a weird
simulation of a "normal" classpath, and it's still possible for apps to notice
- this. Again, java.class.path may not be what you'd expect ("why does it
contain
+ this. Again, <<<java.class.path>>> may not be what you'd expect ("why does it
contain
only one jar?"). Additionally, it's possible to query the system classloader
to
get the list of jars back out of it; your app may be confused if it finds only
- our booter.jar there!
+ our <<<booter.jar>>> there!
* Advantages/Disadvantages of each solution
@@ -122,26 +122,26 @@ java -classpath booter.jar MyApp
* What does Surefire do?
Surefire provides a mechanism for using multiple strategies. The main
parameter that
- determines this is called "useSystemClassLoader". If useSystemClassLoader is
- true, then we use a manifest-only jar; otherwise, we use an isolated
+ determines this is called <<<useSystemClassLoader>>>. If
<<<useSystemClassLoader>>> is
+ <<<true>>>, then we use a manifest-only JAR; otherwise, we use an isolated
classloader. If you want to use a basic plain old Java classpath, you can set
- useManifestOnlyJar=false which only has an effect when
useSystemClassLoader=true.
+ <<<useManifestOnlyJar=false>>> which only has an effect when
<<<useSystemClassLoader=true>>>.
- (The default value for useSystemClassLoader changed between Surefire 2.3 and
+ The default value for <<<useSystemClassLoader>>> changed between Surefire 2.3
and
Surefire 2.4, which was a pretty significant change. In Surefire 2.3,
- useSystemClassLoader was false by default, and we used an isolated
classloader.
- In Surefire 2.4, useSystemClassLoader is true by default. No value works for
+ <<<useSystemClassLoader>>> was <<<false>>> by default, and we used an
isolated classloader.
+ In Surefire 2.4, <<<useSystemClassLoader>>> is <<<true>>> by default. No
value works for
everyone, but we think this default is an improvement; a bunch of
- hard-to-diagnose bugs get better when we useSystemClassLoader=true.)
+ hard-to-diagnose bugs get better when we <<<useSystemClassLoader=true>>>.
- Unfortunately, if useSystemClassLoader is set incorrectly for your app,
you're going to
+ Unfortunately, if <<<useSystemClassLoader>>> is set incorrectly for your app,
you're going to
have a problem on your hands that can be quite difficult to diagnose. You
might
even be forced to read a long doc page like this one. ;-)
- If you're having problems loading classes, try setting
useSystemClassLoader=false
+ If you're having problems loading classes, try setting
<<<useSystemClassLoader=false>>>
to see if that helps. You can do that with the POM snippet below, or by
setting
- "-Dsurefire.useSystemClassLoader=false". If that doesn't work, try setting
- useSystemClassLoader back to true and setting useManifestOnlyJar to false.
+ <<<-Dsurefire.useSystemClassLoader=false>>>. If that doesn't work, try
setting
+ <<<useSystemClassLoader>>> back to <<<true>>> and setting
<<<useManifestOnlyJar>>> to <<<false>>>.
+---+
<project>
@@ -182,8 +182,8 @@ java -classpath booter.jar MyApp
* Run mvn with --debug (aka -X) to get more detailed output
- * Check your forkMode. If forkMode=never, it's impossible to use the system
classloader or a plain old Java classpath; we have to use an isolated
classloader.
+ * Check your <<<forkMode>>>. If <<<forkMode=never>>>, it's impossible to use
the system classloader or a plain old Java classpath; we have to use an
isolated classloader.
- * If you're using the defaults, useSystemClassLoader=true and
useManifestOnlyJar=false. In that case, look at the generated manifest-only
surefire booter jar. Open it up (it's just a zip) and read its manifest.
+ * If you're using the defaults, <<<useSystemClassLoader=true>>> and
<<<useManifestOnlyJar=false>>>. In that case, look at the generated
manifest-only Surefire booter JAR. Open it up (it's just a zip) and read its
manifest.
* Run mvn with -Dmaven.failsafe.debug, and attach to the running process with
a debugger.
\ No newline at end of file
Copied:
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/configuring-classpath.apt.vm
(from r1140122,
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/additional-classpath.apt.vm)
URL:
http://svn.apache.org/viewvc/maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/configuring-classpath.apt.vm?p2=maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/configuring-classpath.apt.vm&p1=maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/additional-classpath.apt.vm&r1=1140122&r2=1140142&rev=1140142&view=diff
==============================================================================
---
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/additional-classpath.apt.vm
(original)
+++
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/configuring-classpath.apt.vm
Mon Jun 27 12:51:21 2011
@@ -1,9 +1,9 @@
------
- Additional Classpath
+ Configuring the Classpath
------
Pascal Lambert
------
- March 2008
+ 2010-01-09
------
~~ Licensed to the Apache Software Foundation (ASF) under one
@@ -26,15 +26,26 @@
~~ NOTE: For help with the syntax of this file, see:
~~ http://maven.apache.org/doxia/references/apt-format.html
+The Default Classpath
+
+ The failsafe plugin builds the test classpath in the following order:
+
+ [[1]] The {{{../test-mojo.html#testClassesDirectory}test-classes}} directory
+
+ [[2]] The {{{../test-mojo.html#classesDirectory}classes}} directory
+
+ [[3]] The project dependencies
+
+ [[4]] Additional classpath elements
Additional Classpath Elements
- If you need to put more stuff in your classpath when Surefire executes (e.g
some funky resources or a container special jar),
+ If you need to put more stuff in your classpath when Surefire executes (e.g
some funky resources or a container specific JAR),
we normally recommend you add it to your classpath as a dependency.
Consider deploying shared jars to a private remote repository for your
organization.
But, if you must, you can use the <<<additionalClasspathElements>>> element
to add custom resources/jars to your classpath.
- This will be treated as an absolute file system path, so you may want use
${basedir} or another property combined with a relative path.
+ This will be treated as an absolute file system path, so you may want use
$\{basedir\} or another property combined with a relative path.
Note that additional classpath elements are added to the end of the
classpath, so you cannot use these to
override project dependencies or resources.
@@ -73,3 +84,87 @@ Additional Classpath Elements
[...]
</project>
+---+
+
+Removing Dependency Classpath Elements
+
+ Dependencies can be removed from the test classpath using the parameters
<<<classpathDependencyExcludes>>> and
+ <<<classpathDependencyScopeExclude>>>. A list of specific dependencies can
be removed from the
+ classpath by specifying the groupId:artifactId to be removed.
+
++---+
+<project>
+ [...]
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>${project.groupId}</groupId>
+ <artifactId>${project.artifactId}</artifactId>
+ <version>${project.version}</version>
+ <configuration>
+ <classpathDependencyExcludes>
+
<classpathDependencyExcludes>org.apache.commons:commons-email</classpathDependencyExcludes>
+ </classpathDependencyExcludes>
+ </configuration>
+ <executions>
+ <execution>
+ <id>integration-test</id>
+ <goals>
+ <goal>integration-test</goal>
+ </goals>
+ </execution>
+ <execution>
+ <id>verify</id>
+ <goals>
+ <goal>verify</goal>
+ </goals>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
+ </build>
+ [...]
+</project>
++---+
+
+ Dependencies under a certain scope can be removed from the classpath using
+ <<<classpathDependencyScopeExclude>>>. The valid values for the dependency
scope
+ exclude are defined by
<<<org.apache.maven.artifact.resolver.filter.ScopeArtifactFilter>>>.
+
+ * <<compile>> - system, provided, compile
+
+ * <<runtime>> - compile, runtime
+
+ * <<test>> - system, provided, compile, runtime, test
+
++---+
+<project>
+ [...]
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>${project.groupId}</groupId>
+ <artifactId>${project.artifactId}</artifactId>
+ <version>${project.version}</version>
+ <configuration>
+
<classpathDependencyScopeExclude>runtime</classpathDependencyScopeExclude>
+ </configuration>
+ <executions>
+ <execution>
+ <id>integration-test</id>
+ <goals>
+ <goal>integration-test</goal>
+ </goals>
+ </execution>
+ <execution>
+ <id>verify</id>
+ <goals>
+ <goal>verify</goal>
+ </goals>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
+ </build>
+ [...]
+</project>
++---+
Propchange:
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/configuring-classpath.apt.vm
------------------------------------------------------------------------------
svn:eol-style = native
Propchange:
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/configuring-classpath.apt.vm
------------------------------------------------------------------------------
svn:keywords = Author Date Id Revision
Modified:
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/debugging.apt
URL:
http://svn.apache.org/viewvc/maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/debugging.apt?rev=1140142&r1=1140141&r2=1140142&view=diff
==============================================================================
---
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/debugging.apt
(original)
+++
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/debugging.apt
Mon Jun 27 12:51:21 2011
@@ -3,7 +3,7 @@
------
Dan Fabulich
------
- January 2008
+ 2010-01-09
------
~~ Licensed to the Apache Software Foundation (ASF) under one
@@ -25,7 +25,6 @@
~~ NOTE: For help with the syntax of this file, see:
~~ http://maven.apache.org/doxia/references/apt-format.html
-
Debugging Tests
@@ -44,7 +43,7 @@ mvn -Dmaven.failsafe.debug verify
using Eclipse. You can setup a "Remote Java Application" launch
configuration via the menu
command "Run" > "Open Debug Dialog..."
- If you need to configure a different port, you may pass a more detailed
value. For example, the value below will use port 8000
+ If you need to configure a different port, you may pass a more detailed
value. For example, the command below will use port 8000
instead of port 5005.
+---+
Modified:
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/inclusion-exclusion.apt.vm
URL:
http://svn.apache.org/viewvc/maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/inclusion-exclusion.apt.vm?rev=1140142&r1=1140141&r2=1140142&view=diff
==============================================================================
---
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/inclusion-exclusion.apt.vm
(original)
+++
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/inclusion-exclusion.apt.vm
Mon Jun 27 12:51:21 2011
@@ -3,7 +3,7 @@
------
Allan Ramirez
------
- July 2006
+ 2010-01-09
------
~~ Licensed to the Apache Software Foundation (ASF) under one
@@ -25,7 +25,6 @@
~~ NOTE: For help with the syntax of this file, see:
~~ http://maven.apache.org/doxia/references/apt-format.html
-
Inclusions and Exclusions of Tests
@@ -34,13 +33,13 @@ Inclusions and Exclusions of Tests
By default, the Failsafe Plugin will automatically include all test classes
with the following wildcard patterns:
- * <"**/IT*.java"> - includes all of its subdirectory and all java
+ * <"**/IT*.java"> - includes all of its subdirectories and all java
filenames that start with "IT".
- * <"**/*IT.java"> - includes all of its subdirectory and all java
+ * <"**/*IT.java"> - includes all of its subdirectories and all java
filenames that end with "IT".
- * <"**/*ITCase.java"> - includes all of its subdirectory and all java
+ * <"**/*ITCase.java"> - includes all of its subdirectories and all java
filenames that end with "ITCase".
[]
@@ -140,7 +139,7 @@ Inclusions and Exclusions of Tests
<plugins>
<plugin>
<groupId>${project.groupId}</groupId>
- <artifactId>maven-surefire-plugin</artifactId>
+ <artifactId>${project.artifactId}</artifactId>
<version>${project.version}</version>
<configuration>
<includes>
Modified:
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/single-test.apt
URL:
http://svn.apache.org/viewvc/maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/single-test.apt?rev=1140142&r1=1140141&r2=1140142&view=diff
==============================================================================
---
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/single-test.apt
(original)
+++
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/single-test.apt
Mon Jun 27 12:51:21 2011
@@ -26,7 +26,6 @@
~~ NOTE: For help with the syntax of this file, see:
~~ http://maven.apache.org/doxia/references/apt-format.html
-
Running a Single Test
Modified:
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/skipping-test.apt.vm
URL:
http://svn.apache.org/viewvc/maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/skipping-test.apt.vm?rev=1140142&r1=1140141&r2=1140142&view=diff
==============================================================================
---
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/skipping-test.apt.vm
(original)
+++
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/skipping-test.apt.vm
Mon Jun 27 12:51:21 2011
@@ -27,7 +27,6 @@
~~ NOTE: For help with the syntax of this file, see:
~~ http://maven.apache.org/doxia/references/apt-format.html
-
Skipping Tests
@@ -72,4 +71,36 @@ mvn install -DskipITs
+---+
mvn install -Dmaven.test.skip=true
-+---+
\ No newline at end of file
++---+
+
+Skipping by default
+
+ If you want to skip tests by default but want the ability to re-enable
tests from the
+ command line, you need to go via a properties section in the pom:
+
++---+
+<properties>
+ <skipTests>true</skipTests>
+</properties>
+
+<build>
+ <plugins>
+ <plugin>
+ <groupId>${project.groupId}</groupId>
+ <artifactId>${project.artifactId}</artifactId>
+ <version>${project.version}</version>
+ <configuration>
+ <skipTests>${skipTests}</skipTests>
+ </configuration>
+ </plugin>
+</plugins>
+</build>
++---+
+
+ This will allow you to run with tests disabled by default and to run them
with this command:
+
++---+
+mvn install -DskipTests=false
++---+
+
+ The same can be done with the "skip" parameter and other booleans on the
plugin.
Modified:
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/system-properties.apt.vm
URL:
http://svn.apache.org/viewvc/maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/system-properties.apt.vm?rev=1140142&r1=1140141&r2=1140142&view=diff
==============================================================================
---
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/system-properties.apt.vm
(original)
+++
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/system-properties.apt.vm
Mon Jun 27 12:51:21 2011
@@ -2,8 +2,9 @@
Using System Properties
------
Allan Ramirez
+ Dan Tran
------
- July 2006
+ 2010-01-09
------
~~ Licensed to the Apache Software Foundation (ASF) under one
@@ -25,16 +26,15 @@
~~ NOTE: For help with the syntax of this file, see:
~~ http://maven.apache.org/doxia/references/apt-format.html
-
Using System Properties
There are two ways to add a list of system properties to Failsafe:
-* systemPropertyVariable
+* systemPropertyVariables
- This configuration is the replacement of the deprecated <systemProperies>.
It can accept any value
- from Maven's properties that can be converted <<to String value>>
+ This configuration is the replacement of the deprecated
<<<systemProperties>>>. It can accept any value
+ from Maven's properties that can be converted <<to String value>>.
+---+
<project>
@@ -101,10 +101,10 @@ Using System Properties
</project>
+---+
- Take note that <<String valued>> properties can only be passed as system
+ Take note that only <<String valued>> properties can be passed as system
properties. Any attempt to pass any other Maven variable type (i.e.
<<<List>>>
or a <<<URL>>> variable) will cause the variable expression to be passed
- literally (unevaluated). So having an example below:
+ literally (unevaluated). So having the example below:
+---+
<project>
@@ -146,3 +146,14 @@ Using System Properties
will literally pass <<$\{project.build.outputDirectory\}>> because the value
of that expression is a <<<File>>>, not a <<<String>>>.
+
+ To inherit the "systemProperties" collection from the parent configuration,
+ you will need to specify combine.children="append" on the systemProperties
node in the child pom:
+
++---+
+ <systemProperties combine.children="append">
+ <property>
+ [...]
+ </property>
+ </systemProperties>
++---+
Modified:
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/testng.apt.vm
URL:
http://svn.apache.org/viewvc/maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/testng.apt.vm?rev=1140142&r1=1140141&r2=1140142&view=diff
==============================================================================
---
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/testng.apt.vm
(original)
+++
maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/examples/testng.apt.vm
Mon Jun 27 12:51:21 2011
@@ -25,19 +25,31 @@
~~ NOTE: For help with the syntax of this file, see:
~~ http://maven.apache.org/doxia/references/apt-format.html
-
Using TestNG
* Configuring TestNG
- To get started with TestNG, include the following dependency in your project:
+ To get started with TestNG, include the following dependency in your project
(replacing the version with the one you wish to use):
+---+
[...]
<dependency>
<groupId>org.testng</groupId>
<artifactId>testng</artifactId>
+ <version>5.12.1</version>
+ <scope>test</scope>
+ </dependency>
+ [...]
++---+
+
+ If you are using an older version of TestNG (\<= 5.11), the dependency would
instead look like this:
+
++---+
+ [...]
+ <dependency>
+ <groupId>org.testng</groupId>
+ <artifactId>testng</artifactId>
<version>5.8</version>
<scope>test</scope>
<classifier>jdk15</classifier>
@@ -45,10 +57,10 @@ Using TestNG
[...]
+---+
- <<Note:>> if you are using JDK 1.4 Javadoc annotations for your TestNG
tests, replace jdk15 with jdk14 above.
+ <<Note:>> if you are using JDK 1.4 Javadoc annotations for your TestNG
tests, replace the classifier <<<jdk15>>> with <<<jdk14>>> above.
This is the only step that is required to get started - you can now create
tests in your test source directory
- (eg, <<<src/test/java>>>, and as long as they are named using the defaults
such as *IT.java they will be run
+ (eg, <<<src/test/java>>>. As long as they are named using the defaults such
as <<<*IT.java>>> they will be run
by Failsafe as TestNG tests.
If you'd like to use a different naming scheme, you can change the
<<<includes>>> parameter, as discussed in the
@@ -57,7 +69,7 @@ Using TestNG
* Using Suite XML Files
Another alternative is to use TestNG suite XML files. This allows flexible
configuration of the tests to be run.
- These files are created as normal, and then added to the Failsafe Plugin
configuration:
+ These files are created in the normal way, and then added to the Failsafe
Plugin configuration:
+---+
[...]
@@ -104,12 +116,9 @@ Using TestNG
<artifactId>${project.artifactId}</artifactId>
<version>${project.version}</version>
<configuration>
- <systemProperties>
- <property>
- <name>browser</name>
- <value>firefox</value>
- </property>
- </systemProperties>
+ <systemPropertyVariables>
+ <propertyName>firefox</propertyName>
+ </systemPropertyVariables>
</configuration>
</plugin>
[...]
@@ -119,7 +128,7 @@ Using TestNG
* Using Groups
- TestNG allows you to group your tests. You can then execute a specific group
or groups. To do this with Failsafe,
+ TestNG allows you to group your tests. You can then execute one or more
specific groups. To do this with Failsafe,
use the <<<groups>>> parameter, for example:
+---+
@@ -194,5 +203,3 @@ Using TestNG
+---+
For more information on TestNG, see the {{{http://www.testng.org}TestNG web
site}}.
-
-
Modified: maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/index.apt
URL:
http://svn.apache.org/viewvc/maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/index.apt?rev=1140142&r1=1140141&r2=1140142&view=diff
==============================================================================
--- maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/index.apt (original)
+++ maven/surefire/trunk/maven-failsafe-plugin/src/site/apt/index.apt Mon Jun
27 12:51:21 2011
@@ -121,6 +121,6 @@ mvn verify
* {{{./examples/system-properties.html}Using System Properties}}
- * {{{./examples/additional-classpath.html}Additional Classpath Elements}}
+ * {{{./examples/configuring-classpath.html}Configuring the Classpath}}
[]
Modified:
maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/class-loading.apt.vm
URL:
http://svn.apache.org/viewvc/maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/class-loading.apt.vm?rev=1140142&r1=1140141&r2=1140142&view=diff
==============================================================================
---
maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/class-loading.apt.vm
(original)
+++
maven/surefire/trunk/maven-surefire-plugin/src/site/apt/examples/class-loading.apt.vm
Mon Jun 27 12:51:21 2011
@@ -54,7 +54,6 @@ It turns out setting the CLASSPATH as an
practical length limitations, as documented in
http://jira.codehaus.org/browse/SUREFIRE-727. This means
most of the length-related problems in this article may be outdated.
-
* How do people solve this problem in general?
There are two "tricks" you can use to workaround this problem; both of them
can cause other problems in some cases.
