You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by kr...@apache.org on 2012/12/06 20:16:44 UTC
[4/6] o Reformatted entire code base to code style
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-plugin/src/site/apt/index.apt.vm
----------------------------------------------------------------------
diff --git a/maven-surefire-plugin/src/site/apt/index.apt.vm b/maven-surefire-plugin/src/site/apt/index.apt.vm
index b27f3f2..5d6f891 100644
--- a/maven-surefire-plugin/src/site/apt/index.apt.vm
+++ b/maven-surefire-plugin/src/site/apt/index.apt.vm
@@ -1,12 +1,12 @@
- ------
- Introduction
- ------
- Stephen Connolly
- Allan Ramirez
- ------
- 2011-06-27
- ------
-
+------
+Introduction
+------
+Stephen Connolly
+Allan Ramirez
+------
+2011-06-27
+------
+
~~ Licensed to the Apache Software Foundation (ASF) under one
~~ or more contributor license agreements. See the NOTICE file
~~ distributed with this work for additional information
@@ -26,127 +26,144 @@
~~ NOTE: For help with the syntax of this file, see:
~~ http://maven.apache.org/doxia/references/apt-format.html
-
+
Maven ${thisPlugin} Plugin
#{if}(${project.artifactId}=="maven-surefire-plugin")
- The Surefire Plugin is used during the <<<test>>> phase of the build
- lifecycle to execute the unit tests of an application. It generates reports
- in 2 different file formats:
+The Surefire Plugin is used during the <<
+<test>>> phase of the build
+ lifecycle to execute the unit tests of an application. It generates reports
+ in 2 different file formats:
#{else}
- The Failsafe Plugin is designed to run integration tests while the Surefire Plugins is designed to run unit tests.
- The name (failsafe) was chosen both because it is a synonym of surefire and because it implies that when it fails, it
- does so in a safe way.
+ The Failsafe Plugin is designed to run integration tests while the Surefire Plugins is designed to run unit tests.
+ The name (failsafe) was chosen both because it is a synonym of surefire and because it implies that when it fails,
+ it
+ does so in a safe way.
- The Maven lifecycle has four phases for running integration tests:
+ The Maven lifecycle has four phases for running integration tests:
- * <<<pre-integration-test>>> for setting up the integration test environment.
+ * <<
+<pre-integration-test>>> for setting up the integration test environment.
- * <<<integration-test>>> for running the integration tests.
+ * <<
+<integration-test>>> for running the integration tests.
- * <<<post-integration-test>>> for tearing down the integration test environment.
+ * <<
+<post-integration-test>>> for tearing down the integration test environment.
- * <<<verify>>> for checking the results of the integration tests.
+ * <<
+<verify>>> for checking the results of the integration tests.
- []
+ []
- If you use the Surefire Plugin for running tests, then when you have a test failure, the build will stop at the
- <<<integration-test>>> phase and your integration test environment will not have been torn down correctly.
+ If you use the Surefire Plugin for running tests, then when you have a test failure, the build will stop at the
+ <<
+<integration-test>>> phase and your integration test environment will not have been torn down correctly.
- The Failsafe Plugin is used during the <<<integration-test>>> and <<<verify>>> phases of the build
- lifecycle to execute the integration tests of an application. The Failsafe Plugin will not fail the build during
- the <<<integration-test>>> phase thus enabling the <<<post-integration-test>>> phase to execute.
+ The Failsafe Plugin is used during the <<
+<integration-test>>> and <<
+<verify>>> phases of the build
+ lifecycle to execute the integration tests of an application. The Failsafe Plugin will not fail the build during
+ the <<
+<integration-test>>> phase thus enabling the <<
+<post-integration-test>>> phase to execute.
- NOTE: when running integration tests, you should invoke maven with the (shorter to type too)
+ NOTE: when running integration tests, you should invoke maven with the (shorter to type too)
-+---+
-mvn verify
-+---+
+ +---+
+ mvn verify
+ +---+
- rather than trying to invoke the <<<integration-test>>> phase directly, as otherwise the <<<post-integration-test>>>
- phase will not be executed.
+ rather than trying to invoke the <<
+<integration-test>>> phase directly, as otherwise the <<
+<post-integration-test>>>
+ phase will not be executed.
- The Failsafe Plugin generates reports in 2 different file formats:
+ The Failsafe Plugin generates reports in 2 different file formats:
#{end}
- * Plain text files (<<<*.txt>>>)
+ * Plain text files (<<<*.txt>>>)
- * XML files (<<<*.xml>>>)
+ * XML files (<<<*.xml>>>)
- []
+ []
- By default, these files are generated at <<<$\{basedir\}/target/${thisPlugin.toLowerCase()}-reports>>>.
+ By default, these files are generated at <<<$\{basedir\}/target/${thisPlugin.toLowerCase()}-reports>>>.
- For an HTML format of the report, please see the
- {{{http://maven.apache.org/plugins/maven-surefire-report-plugin/}Maven Surefire Report Plugin}}.
+ For an HTML format of the report, please see the
+ {{{http://maven.apache.org/plugins/maven-surefire-report-plugin/}Maven Surefire Report Plugin}}.
-* Goals Overview
+ * Goals Overview
#{if}(${project.artifactId}=="maven-surefire-plugin")
- The Surefire Plugin has only 1 goal:
+ The Surefire Plugin has only 1 goal:
- * {{{./test-mojo.html}surefire:test}} runs the unit tests of an application.
+ * {{{./test-mojo.html}surefire:test}} runs the unit tests of an application.
- []
+ []
#{else}
- The Failsafe Plugin has only 2 goals:
+ The Failsafe Plugin has only 2 goals:
- * {{{./integration-test-mojo.html}failsafe:integration-test}} runs the integration tests of an application.
+ * {{{./integration-test-mojo.html}failsafe:integration-test}} runs the integration tests of an application.
- * {{{./verify-mojo.html}failsafe:verify}} verifies that the integration tests of an application passed.
+ * {{{./verify-mojo.html}failsafe:verify}} verifies that the integration tests of an application passed.
- []
+ []
#{end}
-* Usage
+ * Usage
- General instructions on how to use the ${thisPlugin} Plugin can be found on the {{{./usage.html}usage page}}. Some more
- specific use cases are described in the examples given below.
- #{if}(${project.artifactId}=="maven-surefire-plugin") Last but not least, users occasionally contribute
- additional examples, tips or errata to the
- {{{http://docs.codehaus.org/display/MAVENUSER/Surefire+Plugin}plugin's wiki page}}.#{end}
+ General instructions on how to use the ${thisPlugin} Plugin can be found on the {{{./usage.html}usage page}}. Some
+ more
+ specific use cases are described in the examples given below.
+#{if}(${project.artifactId}=="maven-surefire-plugin") Last but not least, users occasionally contribute
+ additional examples, tips or errata to the
+ {{{http://docs.codehaus.org/display/MAVENUSER/Surefire+Plugin}plugin's wiki page}}.#{end}
- In case you still have questions regarding the plugin's usage, please have a look at the {{{./faq.html}FAQ}} and feel
- free to contact the {{{./mail-lists.html}user mailing list}}. The posts to the mailing list are archived and could
- already contain the answer to your question as part of an older thread. Hence, it is also worth browsing/searching
- the {{{./mail-lists.html}mail archive}}.
+ In case you still have questions regarding the plugin's usage, please have a look at the {{{./faq.html}FAQ}} and
+ feel
+ free to contact the {{{./mail-lists.html}user mailing list}}. The posts to the mailing list are archived and could
+ already contain the answer to your question as part of an older thread. Hence, it is also worth browsing/searching
+ the {{{./mail-lists.html}mail archive}}.
- If you feel like the plugin is missing a feature or has a defect, you can fill a feature request or bug report in our
- {{{./issue-tracking.html}issue tracker}}. When creating a new issue, please provide a comprehensive description of your
- concern. Especially for fixing bugs it is crucial that the developers can reproduce your problem. For this reason,
- entire debug logs, POMs or most preferably little demo projects attached to the issue are very much appreciated.
- Of course, patches are welcome, too. Contributors can check out the project from our
- {{{./source-repository.html}source repository}} and will find supplementary information in the
- {{{http://maven.apache.org/guides/development/guide-helping.html}guide to helping with Maven}}.
+ If you feel like the plugin is missing a feature or has a defect, you can fill a feature request or bug report in
+ our
+ {{{./issue-tracking.html}issue tracker}}. When creating a new issue, please provide a comprehensive description of
+ your
+ concern. Especially for fixing bugs it is crucial that the developers can reproduce your problem. For this reason,
+ entire debug logs, POMs or most preferably little demo projects attached to the issue are very much appreciated.
+ Of course, patches are welcome, too. Contributors can check out the project from our
+ {{{./source-repository.html}source repository}} and will find supplementary information in the
+ {{{http://maven.apache.org/guides/development/guide-helping.html}guide to helping with Maven}}.
-* Examples
+ * Examples
- The following examples show how to use the ${thisPlugin} Plugin in more advanced use-cases:
+ The following examples show how to use the ${thisPlugin} Plugin in more advanced use-cases:
- * {{{./examples/testng.html}Using TestNG}}
+ * {{{./examples/testng.html}Using TestNG}}
- * {{{./examples/junit.html}Using JUnit}}
+ * {{{./examples/junit.html}Using JUnit}}
- * {{{./examples/pojo-test.html}Using POJO Tests}}
+ * {{{./examples/pojo-test.html}Using POJO Tests}}
- * {{{./examples/skipping-test.html}Skipping Tests}}
+ * {{{./examples/skipping-test.html}Skipping Tests}}
- * {{{./examples/inclusion-exclusion.html}Inclusions and Exclusions of Tests}}
+ * {{{./examples/inclusion-exclusion.html}Inclusions and Exclusions of Tests}}
- * {{{./examples/single-test.html}Running a Single Test}}
+ * {{{./examples/single-test.html}Running a Single Test}}
- * {{{./examples/class-loading.html}Class Loading Issues}}
+ * {{{./examples/class-loading.html}Class Loading Issues}}
- * {{{./examples/debugging.html}Debugging Tests}}
+ * {{{./examples/debugging.html}Debugging Tests}}
- * {{{./examples/system-properties.html}Using System Properties}}
+ * {{{./examples/system-properties.html}Using System Properties}}
- * {{{./examples/configuring-classpath.html}Configuring the Classpath}}
+ * {{{./examples/configuring-classpath.html}Configuring the Classpath}}
- * {{{./examples/providers.html}Selecting providers}}
+ * {{{./examples/providers.html}Selecting providers}}
- []
+ []
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-plugin/src/site/apt/usage.apt.vm
----------------------------------------------------------------------
diff --git a/maven-surefire-plugin/src/site/apt/usage.apt.vm b/maven-surefire-plugin/src/site/apt/usage.apt.vm
index 53dc424..f32c5b0 100644
--- a/maven-surefire-plugin/src/site/apt/usage.apt.vm
+++ b/maven-surefire-plugin/src/site/apt/usage.apt.vm
@@ -1,13 +1,13 @@
- ------
- Usage
- ------
- Brett Porter
- Allan Ramirez
- Stephen Connolly
- ------
- 2011-06-27
- ------
-
+------
+Usage
+------
+Brett Porter
+Allan Ramirez
+Stephen Connolly
+------
+2011-06-27
+------
+
~~ Licensed to the Apache Software Foundation (ASF) under one
~~ or more contributor license agreements. See the NOTICE file
~~ distributed with this work for additional information
@@ -31,67 +31,72 @@
Usage
#{if}(${project.artifactId}=="maven-surefire-plugin")
- Best practice is to define the version of the Surefire plugin that you want to use in either your <<<pom.xml>>>
- or a parent <<<pom.xml>>>
+Best practice is to define the version of the Surefire plugin that you want to use in either your <<
+<pom.xml>>>
+or a parent <<
+<pom.xml>>>
+---+
<project>
- [...]
- <build>
- <pluginManagement>
- <plugins>
- <plugin>
- <groupId>${project.groupId}</groupId>
- <artifactId>${project.artifactId}</artifactId>
- <version>${project.version}</version>
- </plugin>
- </plugins>
- </pluginManagement>
- </build>
- [...]
+ [...]
+ <build>
+ <pluginManagement>
+ <plugins>
+ <plugin>
+ <groupId>${project.groupId}</groupId>
+ <artifactId>${project.artifactId}</artifactId>
+ <version>${project.version}</version>
+ </plugin>
+ </plugins>
+ </pluginManagement>
+ </build>
+ [...]
</project>
+---+
#{else}
- To use the ${thisPlugin} Plugin, you need to add the following configuration to
- your <<<pom.xml>>>
+To use the ${thisPlugin} Plugin, you need to add the following configuration to
+your <<
+<pom.xml>>>
+---+
<project>
- [...]
- <build>
- <plugins>
- <plugin>
- <groupId>${project.groupId}</groupId>
- <artifactId>${project.artifactId}</artifactId>
- <version>${project.version}</version>
- <executions>
- <execution>
- <goals>
- <goal>integration-test</goal>
- <goal>verify</goal>
- </goals>
- </execution>
- </executions>
- </plugin>
- </plugins>
- </build>
- [...]
+ [...]
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>${project.groupId}</groupId>
+ <artifactId>${project.artifactId}</artifactId>
+ <version>${project.version}</version>
+ <executions>
+ <execution>
+ <goals>
+ <goal>integration-test</goal>
+ <goal>verify</goal>
+ </goals>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
+ </build>
+ [...]
</project>
+---+
#{end}
#{if}(${project.artifactId}=="maven-surefire-plugin")
- The ${thisPlugin} Plugin can be invoked by calling the <<<test>>> phase of the
- build lifecycle.
+The ${thisPlugin} Plugin can be invoked by calling the <<
+<test>>> phase of the
+build lifecycle.
+---+
mvn test
+---+
#{else}
- The ${thisPlugin} Plugin can be invoked by calling the <<<verify>>> phase of the
- build lifecycle.
+The ${thisPlugin} Plugin can be invoked by calling the <<
+<verify>>> phase of the
+build lifecycle.
+---+
mvn verify
@@ -100,341 +105,372 @@ mvn verify
* Using different testing providers
- Tests in your test source directory can be any combination of the following:
+Tests in your test source directory can be any combination of the following:
- * TestNG
+* TestNG
- * JUnit (3.8 or 4.x)
+* JUnit (3.8 or 4.x)
- * POJO
+* POJO
- Which providers are available is controlled simply by the inclusion of the
- appropriate dependencies (ie, junit:junit for JUnit, org.testng:testng 4.7+
- for TestNG). Since this is required to compile the test classes anyway, no
- additional configuration is required.
+Which providers are available is controlled simply by the inclusion of the
+appropriate dependencies (ie, junit:junit for JUnit, org.testng:testng 4.7+
+for TestNG). Since this is required to compile the test classes anyway, no
+additional configuration is required.
- Note that any normal Surefire integration works identically no matter which
- providers are in use - so you can still produce a Cobertura report and a
- Surefire results report on your project web site for your TestNG tests,
- for example.
+Note that any normal Surefire integration works identically no matter which
+providers are in use - so you can still produce a Cobertura report and a
+Surefire results report on your project web site for your TestNG tests,
+for example.
- The POJO provider above allows you to write tests that do not depend on
- JUnit. They behave in the same way, running all <<<test*>>> methods that are
- public in the class, but the API dependency is not required. To perform
- assertions, the JDK 1.4 <<<assert>>> keyword can be used.
- See {{{./examples/pojo-test.html} using POJO tests}} for more information.
+The POJO provider above allows you to write tests that do not depend on
+JUnit. They behave in the same way, running all <<
+<test*>>> methods that are
+public in the class, but the API dependency is not required. To perform
+assertions, the JDK 1.4 <<
+<assert>>> keyword can be used.
+See {{{./examples/pojo-test.html} using POJO tests}} for more information.
- All of the providers support the Surefire Plugin parameter configurations.
- However, there are additional options available if you are running TestNG
- tests (including if you are using TestNG to execute your JUnit tests, which
- occurs by default if both are present in Surefire).
+All of the providers support the Surefire Plugin parameter configurations.
+However, there are additional options available if you are running TestNG
+tests (including if you are using TestNG to execute your JUnit tests, which
+occurs by default if both are present in Surefire).
- See {{{./examples/testng.html} Using TestNG}} for more information.
+See {{{./examples/testng.html} Using TestNG}} for more information.
#{if}(${project.artifactId}=="maven-failsafe-plugin")
* Using jetty and ${project.artifactId}
- You need to bind one of <<<jetty:run>>>, <<<jetty:run-exploded>>> or <<<jetty:run-war>>>
- to the <<<pre-integration-test>>> phase with <<<deamon>>> set to true, bind
- <<<failsafe:integration-test>>> to the <<<integration-test>>> phase, bind <<<jetty:stop>>>
- to the <<<post-integration-test>>> phase and finally bind <<<failsafe:verify>>> to
- the <<<verify>>> phase. Here is an example:
+You need to bind one of <<
+<jetty:run>>>, <<
+<jetty:run-exploded>>> or <<
+<jetty:run-war>>>
+to the <<
+<pre-integration-test>>> phase with <<
+<deamon>>> set to true, bind
+<<
+<failsafe:integration-test>>> to the <<
+<integration-test>>> phase, bind <<
+<jetty:stop>>>
+to the <<
+<post-integration-test>>> phase and finally bind <<
+<failsafe:verify>>> to
+the <<
+<verify>>> phase. Here is an example:
+---+
<project>
- [...]
- <build>
[...]
- <plugins>
- [...]
- <plugin>
- <groupId>${project.groupId}</groupId>
- <artifactId>${project.artifactId}</artifactId>
- <version>${project.version}</version>
- <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>
- <plugin>
- <groupId>org.mortbay.jetty</groupId>
- <artifactId>maven-jetty-plugin</artifactId>
- <version>6.1.16</version>
- [...]
- <configuration>
- [...]
- <scanIntervalSeconds>10</scanIntervalSeconds>
- <stopPort>8005</stopPort>
- <stopKey>STOP</stopKey>
- <contextPath>/</contextPath>
- [...]
- </configuration>
+ <build>
[...]
- <executions>
- [...]
- <execution>
- <id>start-jetty</id>
- <phase>pre-integration-test</phase>
- <goals>
- <goal>run-exploded</goal>
- </goals>
- <configuration>
- <scanIntervalSeconds>0</scanIntervalSeconds>
- <daemon>true</daemon>
- </configuration>
- </execution>
- <execution>
- <id>stop-jetty</id>
- <phase>post-integration-test</phase>
- <goals>
- <goal>stop</goal>
- </goals>
- </execution>
- [...]
- </executions>
+ <plugins>
+ [...]
+ <plugin>
+ <groupId>${project.groupId}</groupId>
+ <artifactId>${project.artifactId}</artifactId>
+ <version>${project.version}</version>
+ <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>
+ <plugin>
+ <groupId>org.mortbay.jetty</groupId>
+ <artifactId>maven-jetty-plugin</artifactId>
+ <version>6.1.16</version>
+ [...]
+ <configuration>
+ [...]
+ <scanIntervalSeconds>10</scanIntervalSeconds>
+ <stopPort>8005</stopPort>
+ <stopKey>STOP</stopKey>
+ <contextPath>/</contextPath>
+ [...]
+ </configuration>
+ [...]
+ <executions>
+ [...]
+ <execution>
+ <id>start-jetty</id>
+ <phase>pre-integration-test</phase>
+ <goals>
+ <goal>run-exploded</goal>
+ </goals>
+ <configuration>
+ <scanIntervalSeconds>0</scanIntervalSeconds>
+ <daemon>true</daemon>
+ </configuration>
+ </execution>
+ <execution>
+ <id>stop-jetty</id>
+ <phase>post-integration-test</phase>
+ <goals>
+ <goal>stop</goal>
+ </goals>
+ </execution>
+ [...]
+ </executions>
+ [...]
+ </plugin>
+ [...]
+ </plugins>
[...]
- </plugin>
- [...]
- </plugins>
+ </build>
[...]
- </build>
- [...]
</project>
+---+
- You then invoke maven with a phase of <<<verify>>> or later in order to run
- the integration tests. DO NOT directly invoke any of the phases:
- <<<pre-integration-test>>>, <<<integration-test>>>, or <<<post-integration-test>>> as
- these are too long to type and they will likely leave a jetty container running.
+You then invoke maven with a phase of <<
+<verify>>> or later in order to run
+the integration tests. DO NOT directly invoke any of the phases:
+<<
+<pre-integration-test>>>, <<
+<integration-test>>>, or <<
+<post-integration-test>>> as
+these are too long to type and they will likely leave a jetty container running.
+---+
mvn verify
+---+
- Note: during test development, you will likely run a jetty instance in the background.
- to help running the integration tests, it can be handy to bind <<<jetty:stop>>> to
- the <<<pre-integration-test>>> phase before <<<jetty:run>>> to flush out any
- running jetty instance before starting the integration test jetty instance, e.g.
+Note: during test development, you will likely run a jetty instance in the background.
+to help running the integration tests, it can be handy to bind <<
+<jetty:stop>>> to
+the <<
+<pre-integration-test>>> phase before <<
+<jetty:run>>> to flush out any
+running jetty instance before starting the integration test jetty instance, e.g.
+---+
<project>
- [...]
- <build>
[...]
- <plugins>
- [...]
- <plugin>
- <groupId>org.mortbay.jetty</groupId>
- <artifactId>maven-jetty-plugin</artifactId>
- <version>6.1.16</version>
+ <build>
[...]
- <executions>
- [...]
- <execution>
- <id>start-jetty</id>
- <phase>pre-integration-test</phase>
- <goals>
- <!-- stop any previous instance to free up the port -->
- <goal>stop</goal>
- <goal>run-exploded</goal>
- </goals>
+ <plugins>
+ [...]
+ <plugin>
+ <groupId>org.mortbay.jetty</groupId>
+ <artifactId>maven-jetty-plugin</artifactId>
+ <version>6.1.16</version>
+ [...]
+ <executions>
+ [...]
+ <execution>
+ <id>start-jetty</id>
+ <phase>pre-integration-test</phase>
+ <goals>
+ <!-- stop any previous instance to free up the port -->
+ <goal>stop</goal>
+ <goal>run-exploded</goal>
+ </goals>
+ [...]
+ </execution>
+ [...]
+ </executions>
+ [...]
+ </plugin>
[...]
- </execution>
- [...]
- </executions>
+ </plugins>
[...]
- </plugin>
- [...]
- </plugins>
+ </build>
[...]
- </build>
- [...]
</project>
+---+
* Reporting integration test results
- The ${thisPlugin} Plugin uses the exact same format as the ${thatPlugin} Plugin, so to generate a report you just add a second
- Surefire Report Plugin report set using the ${thisPlugin} reports directory, e.g.
+The ${thisPlugin} Plugin uses the exact same format as the ${thatPlugin} Plugin, so to generate a report you just add a
+second
+Surefire Report Plugin report set using the ${thisPlugin} reports directory, e.g.
+---+
<project>
- [...]
- <reporting>
- <plugins>
- <plugin>
- <groupId>${project.groupId}</groupId>
- <artifactId>maven-surefire-report-plugin</artifactId>
- <version>${project.version}</version>
- <reportSets>
- <reportSet>
- <id>integration-tests</id>
- <reports>
- <report>failsafe-report-only</report>
- </reports>
- </reportSet>
- </plugin>
- </plugins>
- </reporting>
- [...]
+ [...]
+ <reporting>
+ <plugins>
+ <plugin>
+ <groupId>${project.groupId}</groupId>
+ <artifactId>maven-surefire-report-plugin</artifactId>
+ <version>${project.version}</version>
+ <reportSets>
+ <reportSet>
+ <id>integration-tests</id>
+ <reports>
+ <report>failsafe-report-only</report>
+ </reports>
+ </reportSet>
+ </plugin>
+ </plugins>
+ </reporting>
+ [...]
</project>
+---+
* Running integration tests multiple times
- If you need to run your integration tests multiple times, just use multiple executions of the <<<integration-test>>>
- goal. You will need to specify a different summary file for each execution, and then configure the <<<verify>>> goal
- with the multiple summary files in order to fail the build when any one execution has failures, e.g.
-
-+---+
-<project>
- [...]
- <reporting>
- <plugins>
- <plugin>
- <groupId>${project.groupId}</groupId>
- <artifactId>${project.artifactId}</artifactId>
- <version>${project.version}</version>
- <executions>
- <execution>
- <id>integration-test-red-bevels</id>
- <goals>
- <goal>integration-test</goal>
- </goals>
- <configuration>
- <systemPropertyVariables>
- <bevels>red</bevels>
- </systemPropertyVariables>
- <summaryFile>target/failsafe-reports/failsafe-summary-red-bevels.xml</summaryFile>
- </configuration>
- </execution>
- <execution>
- <id>integration-test-no-bevels</id>
- <goals>
- <goal>integration-test</goal>
- </goals>
- <configuration>
- <systemPropertyVariables>
- <bevels>none</bevels>
- </systemPropertyVariables>
- <summaryFile>target/failsafe-reports/failsafe-summary-no-bevels.xml</summaryFile>
- </configuration>
- </execution>
- <execution>
- <id>verify</id>
- <goals>
- <goal>verify</goal>
- </goals>
- <configuration>
- <summaryFiles>
- <summaryFile>target/failsafe-reports/failsafe-summary-red-bevels.xml</summaryFile>
- <summaryFile>target/failsafe-reports/failsafe-summary-no-bevels.xml</summaryFile>
- </summaryFiles>
- </configuration>
- </execution>
- </executions>
- </plugin>
- </plugins>
- </reporting>
- [...]
-</project>
-+---+
-
-* Using in multi-module projects
-
- The recommendations for using the ${thisPlugin} Plugin listed at the top of this page are fine for 95% of use cases.
- When you are defining a shared definition of the ${thisPlugin} Plugin in a parent pom, it is considered best practice
- to define an execution id in order to allow child projects to override the configuration. Thus you might have the
- following in your parent <<<pom.xml>>>
+If you need to run your integration tests multiple times, just use multiple executions of the <<
+<integration-test>>>
+ goal. You will need to specify a different summary file for each execution, and then configure the <<
+ <verify>>> goal
+ with the multiple summary files in order to fail the build when any one execution has failures, e.g.
-+---+
-<project>
- [...]
- <build>
- <pluginManagement>
- <plugins>
- <plugin>
- <groupId>${project.groupId}</groupId>
- <artifactId>${project.artifactId}</artifactId>
- <version>${project.version}</version>
- <executions>
- <execution>
- <id>integration-test</id>
- <goals>
- <goal>integration-test</goal>
- <goal>verify</goal>
- </goals>
- </execution>
- </executions>
- </plugin>
- </plugins>
- </pluginManagement>
- </build>
- [...]
-</project>
-+---+
-
- The child projects can then trigger usage of the ${thisPlugin} Plugin with
-
-+---+
-<project>
- [...]
- <build>
- <plugins>
- <plugin>
- <groupId>${project.groupId}</groupId>
- <artifactId>${project.artifactId}</artifactId>
- <version>${project.version}</version>
- </plugin>
- </plugins>
- </build>
- [...]
-</project>
-+---+
-
- For very complex builds, it may be better to separate the executions for the <<<integration-test>>> and <<<verify>>>
- goals.
-
-+---+
-<project>
- [...]
- <build>
- <pluginManagement>
- <plugins>
- <plugin>
- <groupId>${project.groupId}</groupId>
- <artifactId>${project.artifactId}</artifactId>
- <version>${project.version}</version>
- <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>
- </pluginManagement>
- </build>
- [...]
-</project>
-+---+
+ +---+
+ <project>
+ [...]
+ <reporting>
+ <plugins>
+ <plugin>
+ <groupId>${project.groupId}</groupId>
+ <artifactId>${project.artifactId}</artifactId>
+ <version>${project.version}</version>
+ <executions>
+ <execution>
+ <id>integration-test-red-bevels</id>
+ <goals>
+ <goal>integration-test</goal>
+ </goals>
+ <configuration>
+ <systemPropertyVariables>
+ <bevels>red</bevels>
+ </systemPropertyVariables>
+ <summaryFile>target/failsafe-reports/failsafe-summary-red-bevels.xml</summaryFile>
+ </configuration>
+ </execution>
+ <execution>
+ <id>integration-test-no-bevels</id>
+ <goals>
+ <goal>integration-test</goal>
+ </goals>
+ <configuration>
+ <systemPropertyVariables>
+ <bevels>none</bevels>
+ </systemPropertyVariables>
+ <summaryFile>target/failsafe-reports/failsafe-summary-no-bevels.xml</summaryFile>
+ </configuration>
+ </execution>
+ <execution>
+ <id>verify</id>
+ <goals>
+ <goal>verify</goal>
+ </goals>
+ <configuration>
+ <summaryFiles>
+ <summaryFile>target/failsafe-reports/failsafe-summary-red-bevels.xml
+ </summaryFile>
+ <summaryFile>target/failsafe-reports/failsafe-summary-no-bevels.xml
+ </summaryFile>
+ </summaryFiles>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
+ </reporting>
+ [...]
+ </project>
+ +---+
+
+ * Using in multi-module projects
+
+ The recommendations for using the ${thisPlugin} Plugin listed at the top of this page are fine for 95% of use
+ cases.
+ When you are defining a shared definition of the ${thisPlugin} Plugin in a parent pom, it is considered best
+ practice
+ to define an execution id in order to allow child projects to override the configuration. Thus you might have
+ the
+ following in your parent <<
+ <pom.xml>>>
+
+ +---+
+ <project>
+ [...]
+ <build>
+ <pluginManagement>
+ <plugins>
+ <plugin>
+ <groupId>${project.groupId}</groupId>
+ <artifactId>${project.artifactId}</artifactId>
+ <version>${project.version}</version>
+ <executions>
+ <execution>
+ <id>integration-test</id>
+ <goals>
+ <goal>integration-test</goal>
+ <goal>verify</goal>
+ </goals>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
+ </pluginManagement>
+ </build>
+ [...]
+ </project>
+ +---+
+
+ The child projects can then trigger usage of the ${thisPlugin} Plugin with
+
+ +---+
+ <project>
+ [...]
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>${project.groupId}</groupId>
+ <artifactId>${project.artifactId}</artifactId>
+ <version>${project.version}</version>
+ </plugin>
+ </plugins>
+ </build>
+ [...]
+ </project>
+ +---+
+
+ For very complex builds, it may be better to separate the executions for the <<
+ <integration-test>>> and <<
+ <verify>>>
+ goals.
+
+ +---+
+ <project>
+ [...]
+ <build>
+ <pluginManagement>
+ <plugins>
+ <plugin>
+ <groupId>${project.groupId}</groupId>
+ <artifactId>${project.artifactId}</artifactId>
+ <version>${project.version}</version>
+ <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>
+ </pluginManagement>
+ </build>
+ [...]
+ </project>
+ +---+
#{end}
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-plugin/src/test/java/org/apache/maven/plugin/surefire/SurefirePluginTest.java
----------------------------------------------------------------------
diff --git a/maven-surefire-plugin/src/test/java/org/apache/maven/plugin/surefire/SurefirePluginTest.java b/maven-surefire-plugin/src/test/java/org/apache/maven/plugin/surefire/SurefirePluginTest.java
index 37aaa45..5252a24 100644
--- a/maven-surefire-plugin/src/test/java/org/apache/maven/plugin/surefire/SurefirePluginTest.java
+++ b/maven-surefire-plugin/src/test/java/org/apache/maven/plugin/surefire/SurefirePluginTest.java
@@ -38,7 +38,7 @@ public class SurefirePluginTest
assertEquals( ForkConfiguration.FORK_ONCE, surefirePlugin.getEffectiveForkMode() );
}
- private void setFieldValue( SurefirePlugin plugin, String fieldName, Object value)
+ private void setFieldValue( SurefirePlugin plugin, String fieldName, Object value )
throws NoSuchFieldException, IllegalAccessException
{
Field field = findField( plugin.getClass(), fieldName );
@@ -47,8 +47,10 @@ public class SurefirePluginTest
}
- private Field findField( Class clazz, String fieldName){
- while (clazz != null){
+ private Field findField( Class clazz, String fieldName )
+ {
+ while ( clazz != null )
+ {
try
{
return clazz.getDeclaredField( fieldName );
@@ -61,7 +63,9 @@ public class SurefirePluginTest
throw new IllegalArgumentException( "Field not found" );
}
- private class MyToolChain implements Toolchain {
+ private class MyToolChain
+ implements Toolchain
+ {
public String getType()
{
return null;
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/pom.xml
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/pom.xml b/maven-surefire-report-plugin/pom.xml
index ca35bc9..d6a64dd 100644
--- a/maven-surefire-report-plugin/pom.xml
+++ b/maven-surefire-report-plugin/pom.xml
@@ -18,7 +18,8 @@
~ under the License.
-->
-<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/FailsafeReportMojo.java
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/FailsafeReportMojo.java b/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/FailsafeReportMojo.java
index 3974142..c2237de 100644
--- a/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/FailsafeReportMojo.java
+++ b/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/FailsafeReportMojo.java
@@ -31,7 +31,6 @@ import org.apache.maven.project.MavenProject;
* See <a href="http://jira.codehaus.org/browse/SUREFIRE-257">http://jira.codehaus.org/browse/SUREFIRE-257</a>
*
* @author Stephen Connolly
- *
* @goal failsafe-report-only
* @execute phase="validate" lifecycle="surefire"
* @since 2.10
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportGenerator.java
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportGenerator.java b/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportGenerator.java
index 10c124f..5e8b842 100644
--- a/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportGenerator.java
+++ b/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportGenerator.java
@@ -215,7 +215,7 @@ public class SurefireReportGenerator
sink.tableRow_();
- for ( Map.Entry<String, List<ReportTestSuite>> entry: suitePackages.entrySet() )
+ for ( Map.Entry<String, List<ReportTestSuite>> entry : suitePackages.entrySet() )
{
sink.tableRow();
@@ -252,7 +252,7 @@ public class SurefireReportGenerator
sink.text( bundle.getString( "report.surefire.text.note2" ) );
sink.paragraph_();
- for ( Map.Entry<String, List<ReportTestSuite>> entry: suitePackages.entrySet() )
+ for ( Map.Entry<String, List<ReportTestSuite>> entry : suitePackages.entrySet() )
{
String packageName = entry.getKey();
@@ -505,7 +505,7 @@ public class SurefireReportGenerator
sink.unknown( "div", new Object[]{ HtmlMarkup.TAG_TYPE_START }, atts );
sink.verbatim( null );
- for ( String line: detail )
+ for ( String line : detail )
{
sink.text( line );
sink.lineBreak();
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportMojo.java
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportMojo.java b/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportMojo.java
index 0981c11..d09ca97 100644
--- a/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportMojo.java
+++ b/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportMojo.java
@@ -27,7 +27,6 @@ import org.apache.maven.project.MavenProject;
* Creates a nicely formatted Surefire Test Report in html format.
*
* @author <a href="mailto:jruiz@exist.com">Johnny R. Ruiz III</a>
- *
* @goal report
* @execute phase="test" lifecycle="surefire"
*/
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportOnlyMojo.java
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportOnlyMojo.java b/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportOnlyMojo.java
index f8f7649..a4208b4 100644
--- a/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportOnlyMojo.java
+++ b/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportOnlyMojo.java
@@ -26,7 +26,6 @@ package org.apache.maven.plugins.surefire.report;
* <a href="http://jira.codehaus.org/browse/SUREFIRE-257">http://jira.codehaus.org/browse/SUREFIRE-257</a>
*
* @author <a href="mailto:baerrach@gmail.com">Barrie Treloar</a>
- *
* @goal report-only
* @execute phase="validate" lifecycle="surefire"
* @since 2.3
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportParser.java
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportParser.java b/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportParser.java
index adf0b3d..1562154 100644
--- a/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportParser.java
+++ b/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportParser.java
@@ -225,7 +225,7 @@ public class SurefireReportParser
{
List<ReportTestCase> failureDetailList = new ArrayList<ReportTestCase>();
- for (ReportTestSuite suite : testSuitesList)
+ for ( ReportTestSuite suite : testSuitesList )
{
List<ReportTestCase> testCaseList = suite.getTestCases();
@@ -265,7 +265,7 @@ public class SurefireReportParser
scanner.setIncludes( StringUtils.split( includes, "," ) );
- scanner.setExcludes( StringUtils.split(excludes, ",") );
+ scanner.setExcludes( StringUtils.split( excludes, "," ) );
scanner.scan();
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/TestSuiteXmlParser.java
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/TestSuiteXmlParser.java b/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/TestSuiteXmlParser.java
index 191024a..49e7c15 100644
--- a/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/TestSuiteXmlParser.java
+++ b/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/TestSuiteXmlParser.java
@@ -81,7 +81,7 @@ public class TestSuiteXmlParser
}
public Collection<ReportTestSuite> parse( InputStream stream )
- throws ParserConfigurationException, SAXException, IOException
+ throws ParserConfigurationException, SAXException, IOException
{
SAXParserFactory factory = SAXParserFactory.newInstance();
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/site/apt/examples/changing-report-name.apt.vm
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/site/apt/examples/changing-report-name.apt.vm b/maven-surefire-report-plugin/src/site/apt/examples/changing-report-name.apt.vm
index 61da62f..15cc561 100644
--- a/maven-surefire-report-plugin/src/site/apt/examples/changing-report-name.apt.vm
+++ b/maven-surefire-report-plugin/src/site/apt/examples/changing-report-name.apt.vm
@@ -1,10 +1,10 @@
- ------
- Changing Report Name
- ------
- Allan Ramirez
- ------
- July 2006
- ------
+------
+Changing Report Name
+------
+Allan Ramirez
+------
+July 2006
+------
~~ Copyright 2006 The Apache Software Foundation.
~~
@@ -25,28 +25,31 @@
Changing Report Name
- In order to configure the file name of the generated report (which is
- <"surefire-report"> by default), the <<outputName>> property should
- be set to its new name.
+In order to configure the file name of the generated report (which is
+<"surefire-report"> by default), the <
+<outputName>> property should
+ be set to its new name.
-+----+
-<project>
- [...]
- <reporting>
- <plugins>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-surefire-report-plugin</artifactId>
- <version>${project.version}</version>
- <configuration>
- <outputName>newname</outputName>
- </configuration>
- </plugin>
- </plugins>
- </reporting>
- [...]
-</project>
-+----+
+ +----+
+ <project>
+ [...]
+ <reporting>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-surefire-report-plugin</artifactId>
+ <version>${project.version}</version>
+ <configuration>
+ <outputName>newname</outputName>
+ </configuration>
+ </plugin>
+ </plugins>
+ </reporting>
+ [...]
+ </project>
+ +----+
- And after executing the <<<mvn site>>>, the generated report file is named
- to <<newname.html>>.
+ And after executing the <<
+ <mvn site>>>, the generated report file is named
+ to <
+ <newname.html>>.
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/site/apt/examples/cross-referencing.apt.vm
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/site/apt/examples/cross-referencing.apt.vm b/maven-surefire-report-plugin/src/site/apt/examples/cross-referencing.apt.vm
index 0714e61..e87600f 100644
--- a/maven-surefire-report-plugin/src/site/apt/examples/cross-referencing.apt.vm
+++ b/maven-surefire-report-plugin/src/site/apt/examples/cross-referencing.apt.vm
@@ -1,10 +1,10 @@
- ------
- Source Code Cross Reference
- ------
- Allan Ramirez
- ------
- July 2006
- ------
+------
+Source Code Cross Reference
+------
+Allan Ramirez
+------
+July 2006
+------
~~ Copyright 2006 The Apache Software Foundation.
~~
@@ -25,54 +25,65 @@
Source Code Cross Reference
- There are times when we need to know right away the line number of the
- source code that caused the failure of the test. The Surefire Report Plugin
- has the capability to cross reference the source code that made the test
- failed. To be able to activate it, the <<<maven-jxr-plugin>>> should
- also be declared in the \<reporting\> section of the POM along with the
- <<<maven-surefire-report-plugin>>>. For more details, please read the
- documentation of the
- {{{http://maven.apache.org/plugins/maven-jxr-plugin/}Maven JXR Plugin}}.
+There are times when we need to know right away the line number of the
+source code that caused the failure of the test. The Surefire Report Plugin
+has the capability to cross reference the source code that made the test
+failed. To be able to activate it, the <<
+<maven-jxr-plugin>>> should
+ also be declared in the \
+ <reporting
+ \> section of the POM along with the
+ <<
+ <maven-surefire-report-plugin>>>. For more details, please read the
+ documentation of the
+ {{{http://maven.apache.org/plugins/maven-jxr-plugin/}Maven JXR Plugin}}.
-+----+
-<project>
- [...]
- <reporting>
- <plugins>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-surefire-report-plugin</artifactId>
- <version>${project.version}</version>
- <configuration>
- <!-- place your configuration here -->
- </configuration>
- </plugin>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-jxr-plugin</artifactId>
- <version>2.1</version>
- </plugin>
- </plugins>
- </reporting>
- [...]
-</project>
-+----+
+ +----+
+ <project>
+ [...]
+ <reporting>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-surefire-report-plugin</artifactId>
+ <version>${project.version}</version>
+ <configuration>
+ <!-- place your configuration here -->
+ </configuration>
+ </plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-jxr-plugin</artifactId>
+ <version>2.1</version>
+ </plugin>
+ </plugins>
+ </reporting>
+ [...]
+ </project>
+ +----+
- After executing <<<mvn site>>> for site generation, You'll notice that from
- the <<Failure Details>> section of the report, the link is available to
- redirect you to the source code that caused the failure.
+ After executing <<
+ <mvn site>>> for site generation, You'll notice that from
+ the <
+ <Failure Details>> section of the report, the link is available to
+ redirect you to the source code that caused the failure.
- From the figure below the code that caused the failure is
- <com.test.proj.AppTest:36>
+ From the figure below the code that caused the failure is
+ <com.test.proj.AppTest:36>
-[../images/failure-details.PNG] Failure Details
+ [../images/failure-details.PNG] Failure Details
- The link will redirect you to the source by clicking it.
+ The link will redirect you to the source by clicking it.
-[../images/xref.PNG] The source
+ [../images/xref.PNG] The source
-* Disable the Cross Reference Link
+ * Disable the Cross Reference Link
- To disable the link to the source code, the <<linkXRef>> property should
- be set to <<false>>. Or another way is by not declaring the
- <<<maven-jxr-plugin>>> to the \<reporting\> section.
+ To disable the link to the source code, the <
+ <linkXRef>> property should
+ be set to <
+ <false>>. Or another way is by not declaring the
+ <<
+ <maven-jxr-plugin>>> to the \
+ <reporting
+ \> section.
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/site/apt/examples/report-custom-location.apt.vm
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/site/apt/examples/report-custom-location.apt.vm b/maven-surefire-report-plugin/src/site/apt/examples/report-custom-location.apt.vm
index ccebf0c..de5babc 100644
--- a/maven-surefire-report-plugin/src/site/apt/examples/report-custom-location.apt.vm
+++ b/maven-surefire-report-plugin/src/site/apt/examples/report-custom-location.apt.vm
@@ -1,10 +1,10 @@
- ------
- Custom Location of the Surefire Report
- ------
- Allan Ramirez
- ------
- July 2006
- ------
+------
+Custom Location of the Surefire Report
+------
+Allan Ramirez
+------
+July 2006
+------
~~ Copyright 2006 The Apache Software Foundation.
~~
@@ -25,48 +25,53 @@
Configuring the Output Location as part of the Project Reports
- To change the location of the generated output report along with other
- project reports. The <<outputDirectory>> property of both
- <<<maven-site-plugin>>> and <<<maven-surefire-report-plugin>>> should be set to the
- new path. For more information, see the documentation of the
- {{{http://maven.apache.org/plugins/maven-site-plugin/}Maven Site Plugin}}.
+To change the location of the generated output report along with other
+project reports. The <
+<outputDirectory>> property of both
+ <<
+ <maven-site-plugin>>> and <<
+ <maven-surefire-report-plugin>>> should be set to the
+ new path. For more information, see the documentation of the
+ {{{http://maven.apache.org/plugins/maven-site-plugin/}Maven Site Plugin}}.
-+----+
-<project>
- [...]
- <reporting>
- <plugins>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-surefire-report-plugin</artifactId>
- <version>${project.version}</version>
- <configuration>
- <outputDirectory>${basedir}/target/newsite</outputDirectory>
- </configuration>
- </plugin>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-site-plugin</artifactId>
- <version>2.1</version>
- <configuration>
- <outputDirectory>${basedir}/target/newsite</outputDirectory>
- </configuration>
- </plugin>
- </plugins>
- </reporting>
- [...]
-</project>
-+----+
+ +----+
+ <project>
+ [...]
+ <reporting>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-surefire-report-plugin</artifactId>
+ <version>${project.version}</version>
+ <configuration>
+ <outputDirectory>${basedir}/target/newsite</outputDirectory>
+ </configuration>
+ </plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-site-plugin</artifactId>
+ <version>2.1</version>
+ <configuration>
+ <outputDirectory>${basedir}/target/newsite</outputDirectory>
+ </configuration>
+ </plugin>
+ </plugins>
+ </reporting>
+ [...]
+ </project>
+ +----+
- Please take note that if the <<outputDirectory>> of the Site Plugin
- is not configured, the output location of the Surefire report will still
- be the default.
+ Please take note that if the <
+ <outputDirectory>> of the Site Plugin
+ is not configured, the output location of the Surefire report will still
+ be the default.
-* Configuring the Output Location using Standalone Goal
+ * Configuring the Output Location using Standalone Goal
- To change the location of the generated output report using the standalone
- goal, the <<outputDirectory>> property should be set to the new path.
+ To change the location of the generated output report using the standalone
+ goal, the <
+ <outputDirectory>> property should be set to the new path.
-+---+
-mvn surefire-report:report -DoutputDirectory=newpath
-+---+
+ +---+
+ mvn surefire-report:report -DoutputDirectory=newpath
+ +---+
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/site/apt/examples/show-failures.apt.vm
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/site/apt/examples/show-failures.apt.vm b/maven-surefire-report-plugin/src/site/apt/examples/show-failures.apt.vm
index 7ee1edd..0fdcd52 100644
--- a/maven-surefire-report-plugin/src/site/apt/examples/show-failures.apt.vm
+++ b/maven-surefire-report-plugin/src/site/apt/examples/show-failures.apt.vm
@@ -1,10 +1,10 @@
- ------
- Showing Failure Tests
- ------
- Allan Ramirez
- ------
- July 2006
- ------
+------
+Showing Failure Tests
+------
+Allan Ramirez
+------
+July 2006
+------
~~ Copyright 2006 The Apache Software Foundation.
~~
@@ -25,33 +25,36 @@
Showing Failure Tests
- By default, the Surefire Report Plugin shows all test result status (success
- and failures) in the generated HTML. To be able to show the failures only, the
- property <<showSuccess>> should be set to <<false>>.
-
-+----+
-<project>
- [...]
- <reporting>
- <plugins>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-surefire-report-plugin</artifactId>
- <version>${project.version}</version>
- <configuration>
- <showSuccess>false</showSuccess>
- </configuration>
- </plugin>
- </plugins>
- </reporting>
- [...]
-</project>
-+----+
-
- Then execute <<<mvn site>>> for the report generation.
-
- It can also be set via commandline with the standalone goal.
-
-+----+
- mvn surefire-report:report -DshowSuccess=false
-+----+
+By default, the Surefire Report Plugin shows all test result status (success
+and failures) in the generated HTML. To be able to show the failures only, the
+property <
+<showSuccess>> should be set to <
+ <false>>.
+
+ +----+
+ <project>
+ [...]
+ <reporting>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-surefire-report-plugin</artifactId>
+ <version>${project.version}</version>
+ <configuration>
+ <showSuccess>false</showSuccess>
+ </configuration>
+ </plugin>
+ </plugins>
+ </reporting>
+ [...]
+ </project>
+ +----+
+
+ Then execute <<
+ <mvn site>>> for the report generation.
+
+ It can also be set via commandline with the standalone goal.
+
+ +----+
+ mvn surefire-report:report -DshowSuccess=false
+ +----+
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/site/apt/usage.apt.vm
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/site/apt/usage.apt.vm b/maven-surefire-report-plugin/src/site/apt/usage.apt.vm
index ef71d13..62ba366 100644
--- a/maven-surefire-report-plugin/src/site/apt/usage.apt.vm
+++ b/maven-surefire-report-plugin/src/site/apt/usage.apt.vm
@@ -1,10 +1,10 @@
- ------
- Usage
- ------
- Allan Ramirez
- ------
- July 2006
- ------
+------
+Usage
+------
+Allan Ramirez
+------
+July 2006
+------
~~ Copyright 2006 The Apache Software Foundation.
~~
@@ -27,39 +27,41 @@ Usage
* Generate the report as part of Project Reports
- To generate the Surefire report as part of the site generation, add the following in
- the \<reporting\> section of your POM:
+To generate the Surefire report as part of the site generation, add the following in
+the \
+<reporting\> section of your POM:
+---+
<project>
- ...
- <reporting>
- <plugins>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-surefire-report-plugin</artifactId>
- <version>${project.version}</version>
- </plugin>
- </plugins>
- </reporting>
- ...
+ ...
+ <reporting>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-surefire-report-plugin</artifactId>
+ <version>${project.version}</version>
+ </plugin>
+ </plugins>
+ </reporting>
+ ...
</project>
+---+
- When the <<<mvn site>>> is invoked, the report will be automatically
- included in the Project Reports menu as shown in the figure below.
+When the <<
+<mvn site>>> is invoked, the report will be automatically
+ included in the Project Reports menu as shown in the figure below.
-[images/surefire-sample1.PNG] Sample Surefire Report
+ [images/surefire-sample1.PNG] Sample Surefire Report
-* Generate the report as standalone
+ * Generate the report as standalone
- The Surefire report can also generate the report using its standalone goal:
+ The Surefire report can also generate the report using its standalone goal:
-+---+
-mvn surefire-report:report
-+---+
+ +---+
+ mvn surefire-report:report
+ +---+
- A HTML report should be generated in <<<$\{basedir\}/target/site/surefire-report.html>>>.
+ A HTML report should be generated in <<<$\{basedir\}/target/site/surefire-report.html>>>.
-[images/surefire-sample2.PNG] Sample standalone surefire-report
+ [images/surefire-sample2.PNG] Sample standalone surefire-report
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/ReportTestCaseTest.java
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/ReportTestCaseTest.java b/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/ReportTestCaseTest.java
index d0b7574..ecf529a 100644
--- a/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/ReportTestCaseTest.java
+++ b/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/ReportTestCaseTest.java
@@ -23,7 +23,6 @@ import junit.framework.TestCase;
/**
* @author Jontri
- *
*/
public class ReportTestCaseTest
extends TestCase
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/SurefireReportMojoTest.java
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/SurefireReportMojoTest.java b/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/SurefireReportMojoTest.java
index a4fca7f..6cbfb08 100644
--- a/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/SurefireReportMojoTest.java
+++ b/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/SurefireReportMojoTest.java
@@ -31,13 +31,12 @@ import org.apache.maven.doxia.siterenderer.RendererException;
import org.apache.maven.doxia.siterenderer.SiteRenderingContext;
import org.apache.maven.doxia.siterenderer.sink.SiteRendererSink;
import org.apache.maven.plugin.testing.AbstractMojoTestCase;
-import org.codehaus.plexus.util.FileUtils;
import org.apache.maven.shared.utils.WriterFactory;
import org.apache.maven.shared.utils.io.IOUtil;
+import org.codehaus.plexus.util.FileUtils;
/**
* @author <a href="mailto:aramirez@apache.org">Allan Ramirez</a>
- *
*/
public class SurefireReportMojoTest
extends AbstractMojoTestCase
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/TestSuiteXmlParserTest.java
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/TestSuiteXmlParserTest.java b/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/TestSuiteXmlParserTest.java
index 2111920..a3f9f3f 100644
--- a/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/TestSuiteXmlParserTest.java
+++ b/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/TestSuiteXmlParserTest.java
@@ -19,12 +19,12 @@ package org.apache.maven.plugins.surefire.report;
* under the License.
*/
-import junit.framework.TestCase;
-
import java.io.ByteArrayInputStream;
import java.io.InputStream;
import java.util.Collection;
+import junit.framework.TestCase;
+
/**
* @author Kristian Rosenvold
*/
@@ -36,36 +36,41 @@ public class TestSuiteXmlParserTest
{
TestSuiteXmlParser testSuiteXmlParser = new TestSuiteXmlParser();
String xml = "<?xml version=\"1.0\" encoding=\"UTF-8\" ?>\n" +
- "<testsuite failures=\"4\" time=\"0.005\" errors=\"0\" skipped=\"0\" tests=\"4\" name=\"wellFormedXmlFailures.TestSurefire3\">\n" +
- " <properties>\n" +
- " <property name=\"java.runtime.name\" value=\"Java(TM) SE Runtime Environment\"/>\n" +
- " <property name=\"sun.cpu.isalist\" value=\"amd64\"/>\n" +
- " </properties>\n" +
- " <testcase time=\"0.005\" classname=\"wellFormedXmlFailures.TestSurefire3\" name=\"testLower\">\n" +
- " <failure message=\"<\" type=\"junit.framework.AssertionFailedError\"><![CDATA[junit.framework.AssertionFailedError: <\n" +
- "\tat junit.framework.Assert.fail(Assert.java:47)\n" +
- "\tat wellFormedXmlFailures.TestSurefire3.testLower(TestSurefire3.java:30)\n" +
- "]]></failure>\n" +
- " </testcase>\n" +
- " <testcase time=\"0\" classname=\"wellFormedXmlFailures.TestSurefire3\" name=\"testU0000\">\n" +
- " <failure message=\"&0#;\" type=\"junit.framework.AssertionFailedError\">junit.framework.AssertionFailedError: \n" +
- "\tat junit.framework.Assert.fail(Assert.java:47)\n" +
- "\tat wellFormedXmlFailures.TestSurefire3.testU0000(TestSurefire3.java:40)\n" +
- "</failure>\n" +
- " </testcase>\n" +
- " <testcase time=\"0\" classname=\"wellFormedXmlFailures.TestSurefire3\" name=\"testGreater\">\n" +
- " <failure message=\">\" type=\"junit.framework.AssertionFailedError\">junit.framework.AssertionFailedError: >\n" +
- "\tat junit.framework.Assert.fail(Assert.java:47)\n" +
- "\tat wellFormedXmlFailures.TestSurefire3.testGreater(TestSurefire3.java:35)\n" +
- "</failure>\n" +
- " </testcase>\n" +
- " <testcase time=\"0\" classname=\"wellFormedXmlFailures.TestSurefire3\" name=\"testQuote\">\n" +
- " <failure message=\""\" type=\"junit.framework.AssertionFailedError\">junit.framework.AssertionFailedError: \"\n" +
- "\tat junit.framework.Assert.fail(Assert.java:47)\n" +
- "\tat wellFormedXmlFailures.TestSurefire3.testQuote(TestSurefire3.java:25)\n" +
- "</failure>\n" +
- " </testcase>\n" +
- "</testsuite>";
+ "<testsuite failures=\"4\" time=\"0.005\" errors=\"0\" skipped=\"0\" tests=\"4\" name=\"wellFormedXmlFailures.TestSurefire3\">\n"
+ +
+ " <properties>\n" +
+ " <property name=\"java.runtime.name\" value=\"Java(TM) SE Runtime Environment\"/>\n" +
+ " <property name=\"sun.cpu.isalist\" value=\"amd64\"/>\n" +
+ " </properties>\n" +
+ " <testcase time=\"0.005\" classname=\"wellFormedXmlFailures.TestSurefire3\" name=\"testLower\">\n" +
+ " <failure message=\"<\" type=\"junit.framework.AssertionFailedError\"><![CDATA[junit.framework.AssertionFailedError: <\n"
+ +
+ "\tat junit.framework.Assert.fail(Assert.java:47)\n" +
+ "\tat wellFormedXmlFailures.TestSurefire3.testLower(TestSurefire3.java:30)\n" +
+ "]]></failure>\n" +
+ " </testcase>\n" +
+ " <testcase time=\"0\" classname=\"wellFormedXmlFailures.TestSurefire3\" name=\"testU0000\">\n" +
+ " <failure message=\"&0#;\" type=\"junit.framework.AssertionFailedError\">junit.framework.AssertionFailedError: \n"
+ +
+ "\tat junit.framework.Assert.fail(Assert.java:47)\n" +
+ "\tat wellFormedXmlFailures.TestSurefire3.testU0000(TestSurefire3.java:40)\n" +
+ "</failure>\n" +
+ " </testcase>\n" +
+ " <testcase time=\"0\" classname=\"wellFormedXmlFailures.TestSurefire3\" name=\"testGreater\">\n" +
+ " <failure message=\">\" type=\"junit.framework.AssertionFailedError\">junit.framework.AssertionFailedError: >\n"
+ +
+ "\tat junit.framework.Assert.fail(Assert.java:47)\n" +
+ "\tat wellFormedXmlFailures.TestSurefire3.testGreater(TestSurefire3.java:35)\n" +
+ "</failure>\n" +
+ " </testcase>\n" +
+ " <testcase time=\"0\" classname=\"wellFormedXmlFailures.TestSurefire3\" name=\"testQuote\">\n" +
+ " <failure message=\""\" type=\"junit.framework.AssertionFailedError\">junit.framework.AssertionFailedError: \"\n"
+ +
+ "\tat junit.framework.Assert.fail(Assert.java:47)\n" +
+ "\tat wellFormedXmlFailures.TestSurefire3.testQuote(TestSurefire3.java:25)\n" +
+ "</failure>\n" +
+ " </testcase>\n" +
+ "</testsuite>";
InputStream byteArrayIs = new ByteArrayInputStream( xml.getBytes() );
Collection<ReportTestSuite> parse = testSuiteXmlParser.parse( byteArrayIs );
}
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/stubs/SurefireRepMavenProjectStub.java
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/stubs/SurefireRepMavenProjectStub.java b/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/stubs/SurefireRepMavenProjectStub.java
index 8b3afcd..af02470 100644
--- a/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/stubs/SurefireRepMavenProjectStub.java
+++ b/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/stubs/SurefireRepMavenProjectStub.java
@@ -27,7 +27,6 @@ import org.apache.maven.plugin.testing.stubs.MavenProjectStub;
/**
* @author <a href="mailto:aramirez@apache.org">Allan Ramirez</a>
- *
*/
public class SurefireRepMavenProjectStub
extends MavenProjectStub
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/stubs/SurefireRepMavenProjectStub2.java
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/stubs/SurefireRepMavenProjectStub2.java b/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/stubs/SurefireRepMavenProjectStub2.java
index 49103fc..18277ca 100644
--- a/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/stubs/SurefireRepMavenProjectStub2.java
+++ b/maven-surefire-report-plugin/src/test/java/org/apache/maven/plugins/surefire/report/stubs/SurefireRepMavenProjectStub2.java
@@ -25,7 +25,6 @@ import org.apache.maven.plugin.testing.stubs.MavenProjectStub;
/**
* @author <a href="mailto:aramirez@apache.org">Allan Ramirez</a>
- *
*/
public class SurefireRepMavenProjectStub2
extends MavenProjectStub
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/test/resources/test-reports/TEST-AntUnit.xml
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/test/resources/test-reports/TEST-AntUnit.xml b/maven-surefire-report-plugin/src/test/resources/test-reports/TEST-AntUnit.xml
index e73025d..71e5342 100644
--- a/maven-surefire-report-plugin/src/test/resources/test-reports/TEST-AntUnit.xml
+++ b/maven-surefire-report-plugin/src/test/resources/test-reports/TEST-AntUnit.xml
@@ -1,5 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
-<testsuite buildFile="/home/pjanes/devel/maven/client/tools/tests/changebase.xml" hostname="merope" name="tests.changebase_xml" timestamp="2008-04-23T13:25:46">
+<testsuite buildFile="/home/pjanes/devel/maven/client/tools/tests/changebase.xml" hostname="merope"
+ name="tests.changebase_xml" timestamp="2008-04-23T13:25:46">
<testcase name="testNegativeValue">
<time>0.378</time>
</testcase>
http://git-wip-us.apache.org/repos/asf/maven-surefire/blob/a303827d/maven-surefire-report-plugin/src/test/resources/test-reports/TEST-classWithNoTests.NoMethodsTestCase.xml
----------------------------------------------------------------------
diff --git a/maven-surefire-report-plugin/src/test/resources/test-reports/TEST-classWithNoTests.NoMethodsTestCase.xml b/maven-surefire-report-plugin/src/test/resources/test-reports/TEST-classWithNoTests.NoMethodsTestCase.xml
index 0a99ed2..31f7ea5 100644
--- a/maven-surefire-report-plugin/src/test/resources/test-reports/TEST-classWithNoTests.NoMethodsTestCase.xml
+++ b/maven-surefire-report-plugin/src/test/resources/test-reports/TEST-classWithNoTests.NoMethodsTestCase.xml
@@ -13,10 +13,14 @@
<property value="SUN_STANDARD" name="sun.java.launcher"/>
<property value="Service Pack 2" name="sun.os.patch.level"/>
<property value="Java Virtual Machine Specification" name="java.vm.specification.name"/>
- <property value="C:\svn\maven\trunks\surefire\surefire-integration-tests\src\test\resources\default-configuration-classWithNoTests" name="user.dir"/>
+ <property
+ value="C:\svn\maven\trunks\surefire\surefire-integration-tests\src\test\resources\default-configuration-classWithNoTests"
+ name="user.dir"/>
<property value="1.5.0_12-b04" name="java.runtime.version"/>
<property value="sun.awt.Win32GraphicsEnvironment" name="java.awt.graphicsenv"/>
- <property value="C:\svn\maven\trunks\surefire\surefire-integration-tests\src\test\resources\default-configuration-classWithNoTests" name="basedir"/>
+ <property
+ value="C:\svn\maven\trunks\surefire\surefire-integration-tests\src\test\resources\default-configuration-classWithNoTests"
+ name="basedir"/>
<property value="C:\devtools\jdk1.5.0_12\jre\lib\endorsed" name="java.endorsed.dirs"/>
<property value="x86" name="os.arch"/>
<property value="C:\DOCUME~1\DAN~1.FAB\LOCALS~1\Temp\" name="java.io.tmpdir"/>
@@ -27,8 +31,12 @@
<property value="Windows XP" name="os.name"/>
<property value="C:\devtools\maven-2.0.8\bin\m2.conf" name="classworlds.conf"/>
<property value="Cp1252" name="sun.jnu.encoding"/>
- <property value="C:\devtools\jdk1.5.0_12\bin;.;C:\WINDOWS\system32;C:\WINDOWS;c:\devtools\apache-ant-1.7.0\bin;C:\Python25;C:\Perl\bin;C:\devtools\php-5.2.3\;c:\devtools\ruby-1.8.6-25\bin;C:\devtools\jdk1.5.0_12\bin;C:\devtools\maven-2.0.8\bin;c:\dan\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\IDM Computer Solutions\UltraEdit-32;C:\Program Files\Subversion\bin;C:\Program Files\cvsnt;C:\Program Files\GNU\GnuPG\pub;c:\cygwin\bin;C:\Program Files\MySQL\MySQL Server 5.0\bin;C:\Program Files\PostgreSQL\8.2\bin;C:\Program Files\Perforce;" name="java.library.path"/>
- <property value="C:\svn\maven\trunks\surefire\surefire-integration-tests\src\test\resources\default-configuration-classWithNoTests\target\test-classes;C:\svn\maven\trunks\surefire\surefire-integration-tests\src\test\resources\default-configuration-classWithNoTests\target\classes;c:\weirdlocalrepo\junit\junit\3.8.1\junit-3.8.1.jar;" name="surefire.test.class.path"/>
+ <property
+ value="C:\devtools\jdk1.5.0_12\bin;.;C:\WINDOWS\system32;C:\WINDOWS;c:\devtools\apache-ant-1.7.0\bin;C:\Python25;C:\Perl\bin;C:\devtools\php-5.2.3\;c:\devtools\ruby-1.8.6-25\bin;C:\devtools\jdk1.5.0_12\bin;C:\devtools\maven-2.0.8\bin;c:\dan\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\IDM Computer Solutions\UltraEdit-32;C:\Program Files\Subversion\bin;C:\Program Files\cvsnt;C:\Program Files\GNU\GnuPG\pub;c:\cygwin\bin;C:\Program Files\MySQL\MySQL Server 5.0\bin;C:\Program Files\PostgreSQL\8.2\bin;C:\Program Files\Perforce;"
+ name="java.library.path"/>
+ <property
+ value="C:\svn\maven\trunks\surefire\surefire-integration-tests\src\test\resources\default-configuration-classWithNoTests\target\test-classes;C:\svn\maven\trunks\surefire\surefire-integration-tests\src\test\resources\default-configuration-classWithNoTests\target\classes;c:\weirdlocalrepo\junit\junit\3.8.1\junit-3.8.1.jar;"
+ name="surefire.test.class.path"/>
<property value="Java Platform API Specification" name="java.specification.name"/>
<property value="49.0" name="java.class.version"/>
<property value="HotSpot Client Compiler" name="sun.management.compiler"/>
@@ -49,7 +57,9 @@
<property value="mixed mode" name="java.vm.info"/>
<property value="1.5.0_12" name="java.version"/>
<property value="C:\devtools\jdk1.5.0_12\jre\lib\ext" name="java.ext.dirs"/>
- <property value="C:\devtools\jdk1.5.0_12\jre\lib\rt.jar;C:\devtools\jdk1.5.0_12\jre\lib\i18n.jar;C:\devtools\jdk1.5.0_12\jre\lib\sunrsasign.jar;C:\devtools\jdk1.5.0_12\jre\lib\jsse.jar;C:\devtools\jdk1.5.0_12\jre\lib\jce.jar;C:\devtools\jdk1.5.0_12\jre\lib\charsets.jar;C:\devtools\jdk1.5.0_12\jre\classes" name="sun.boot.class.path"/>
+ <property
+ value="C:\devtools\jdk1.5.0_12\jre\lib\rt.jar;C:\devtools\jdk1.5.0_12\jre\lib\i18n.jar;C:\devtools\jdk1.5.0_12\jre\lib\sunrsasign.jar;C:\devtools\jdk1.5.0_12\jre\lib\jsse.jar;C:\devtools\jdk1.5.0_12\jre\lib\jce.jar;C:\devtools\jdk1.5.0_12\jre\lib\charsets.jar;C:\devtools\jdk1.5.0_12\jre\classes"
+ name="sun.boot.class.path"/>
<property value="Sun Microsystems Inc." name="java.vendor"/>
<property value="C:\devtools\maven-2.0.8" name="maven.home"/>
<property value="c:\weirdlocalrepo" name="localRepository"/>