maven3 enforces the good practice of using timestamped snapshots (by dropping
support for uniqueVersion=false) so I had no choice but to try and get it to
work, even though I was just fine with non-unique snapshots.
My project setup is pretty typical: projectA depends on projectB which
depends on
o, it is enough to explicitly define
false in the execution of the
surefire plugin or define the system property
-Dmaven.test.failure.ignore=false to prevent the override. I tested it and
it works. Huray!
Bogdan Calmac wrote:
>
> OK, I've also tested with a simple maven projects and (as
OK, I've also tested with a simple maven projects and (as you mentioned) the
artifacts are still deployed even after the tests fail.
Now irrespective of the color of the balls and what hudson does on its side,
I expect mvn to behave the same on hudson and cmd-line. If maven does not
deploy artif
OK, I've done some further investigation and discovered that this only
happens on our Hudson CI server. The cmdline maven build works as expected.
For reference, here is the JIRA for the Hudson project:
http://issues.hudson-ci.org/browse/HUDSON-8065
--
View this message in context:
http://maven
No, I don't necessarily want to decouple the tests from the build. It's also
OK if the build fails after running only the mssql tests. The only thing is
that I don't want the build to succeed when after of the test executions
failed.
--
View this message in context:
http://maven.40175.n5.nabble.
Our project is configured to run the unit tests twice, with oracle and mssql
databases. This is achieved by configuring two executions of the surefire
plugin and passing in a different system property. Here is the relevant
snippet from the POM:
org.apache.maven.plugins
redirectTestOutputToFile is false by default so the output already goes to
the console, just as I want. However this does not include the test results.
The solution is useFile=false (I missed this).
However, this is a misnomer, it should be called enableConsoleTestResults,
because the HTML test
In the old ant world, the testng plugin would print the test results to
stdout (in addition to the HTML report). This was very convenient when
running the build from eclipse; I could see the failures right in the
console window and click on the links for stacktraces.
In contrast, the surefire plu
Thanks, easy enough.
surefire.useFile=false
--
View this message in context:
http://maven.40175.n5.nabble.com/Surefire-can-you-print-TestNG-results-to-stdout-tp2798735p2798817.html
Sent from the Maven - Users mailing list archive at Nabble.com.
In the old ant world, the testng plugin would print the test results to
stdout (in addition to the HTML report). This was very convenient when
running the build from eclipse; I could see the failures right in the
console window and click on the links for stacktraces.
In contrast, the surefire plu
10 matches
Mail list logo