[SUREFIRE-1385] System properties defined in the Surefire and Failsafe plugin configuration should override user properties

When building the Surefire properties, user properties should be set first so that the more direct configuration of systemPropertyVariables and systemPropertyFile can possibly override them.
5 files changed
tree: 841b4786aeac2f95662cf56dad8ed522b06ab622
  1. .gitattributes
  2. .gitignore
  4. Jenkinsfile
  5. README.md
  6. deploySite.sh
  7. maven-failsafe-plugin/
  8. maven-surefire-common/
  9. maven-surefire-plugin/
  10. maven-surefire-report-plugin/
  11. pom.xml
  12. src/
  13. surefire-api/
  14. surefire-booter/
  15. surefire-grouper/
  16. surefire-integration-tests/
  17. surefire-logger-api/
  18. surefire-providers/
  19. surefire-report-parser/
  20. surefire-setup-integration-tests/
  21. surefire-shadefire/

Built with Maven CI

chat Join us @ irc://freenode/maven or Webchat with us @channel maven

Release Notes

Maven Central

JIRA Change Log


Usage of maven-surefire-plugin, maven-failsafe-plugin, maven-surefire-report-plugin.

Project Documentation


Build Status

dependencies Maven 2.2.1 Plugin API

license coverage tests Build Status Build Status Build Status

Development Information

Surefire needs to use Maven 3.1.0+ and JDK 1.6+ to be built. But in order to run IT tests, you can do:

  • In order to run tests for a release check during the vote the following memory requirements are needed: $ export MAVEN_OPTS=“-Xmx768m -XX:MaxPermSize=1g -XX:SoftRefLRUPolicyMSPerMB=50 -Djava.awt.headless=true”
  • $ mvn install site site:stage -P reporting,run-its

Deploying web site

see http://maven.apache.org/developers/website/deploy-component-reference-documentation.html