Karl Heinz Marbaise wrote:
I have observed that behaviour with maven-surefire 2.7.1 (in relationship with Maven 3.0.1) but i use maven-surefire plugin 2.4.3...(see http://jira.codehaus.org/browse/SUREFIRE-680)
From your build's log:
[INFO] --- maven-surefire-plugin:2.7.1:test (default-test) @ licenses-verifier --- [INFO] Surefire report directory: M:\Maven-Licenses-Verifier-Plugin\licenses-verifier\target\surefire-reports
which matches the observation that your POM locks down maven-surefire-report-plugin to 2.4.3 but not maven-surefire-plugin.
Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
