You might want to try the following:
if you don't already have a global pom properties tag you would add one.
Then in the body of the properties tag you would add the following 2
tags and their values:
<properties>
<surefire.useFile>false</surefire.useFile>
<surefire.reportFormat>plain</surefire.reportFormat>
</properties>
If I remember correctly, the surefire plugin will honor these properties
unless you have overridden them in your surefire plugin configuration.
It provides a simple mechanism to get an idea of what surefire/junit is
doing without actually adding a surefire declaration to your build
section at all.
Alternatively, you could add the tags:
<configuration>
<userFile>false<useFile>
<reportFormat>plain</reportFormat>
</configuration>
to the configuration section of your surefire plugin declaration, if you
have one.
I prefer to set the properties at the global properties level as it
saves me the expense of including the surefire plugin declaration.
On 9/27/11 3:26 AM, arka.sharma wrote:
*Surefire Report
Summary
Tests Errors Failures Skipped Success Rate Time
0 0 0 0 0% 0
Note: failures are anticipated and checked for with assertions while errors
are unanticipated.*
This is the report t*arget/site/surefire-report.html* after doing *mvn
surefire-report:report-only*
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-fails-to-run-junit-test-sources-tp4844249p4844334.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
