On Friday 11 July 2008 Carlos Alonso wrote: > You're right Martin, but, as I explained in my first mail, the state > build succeeds has also two states, depending on the stability of the > product.
But not for maven! > The stability of the product depends on the test cases, if every test > case passes, the product is stable, otherwise, unstable. But the build > process is successful in both cases because the code is successfully > compiled and packaged. > Imagine the following scenario: > > For some reason, the computer where the whole process is launched has > lost it's Internet connection and, a test that depends on XML fails > because the page where to retrieve the .xsd file cannot be reached. > There is also a second test that is really broken. Both tests will fail > but the build will succeed. When looking at the generated report, you'll > see that one of the tests where really broken while the other failed due > to the network problem. > If the whole build was considered as a failure, no test report could be > found, and, no information further than 2 Tests failed could be gathered. I got what you want, but maven doesn't support this. Maybe you can achieve your goal somehow with maven, but it would be an ugly hack. Use "mvn site" to creat reports, this will succeed even if the build itself is broken, so you get your reports. hth, - martin
signature.asc
Description: This is a digitally signed message part.
