This wasn't the information I was asking for. What do the test reports say? For the tests I had that were failing, there were two reasons: security failures (for the test that require a security manager I needed to add some additional permissions to the policy file) and test code trying to find some files on the hard drive (because the tests when run by JCoverage are in a different location).
At this point, all of our projects are working successfully with JCoverage. We're not using JDK1.5, however. ..David.. -----Original Message----- From: J�rg Schaible [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 27, 2005 7:34 AM To: Maven Users List Subject: RE: Test-plugin versus jcoverage-plugin? Hi Darren, Darren Hartford wrote on Wednesday, April 27, 2005 3:31 PM: > Hi David, > When running "maven test", I get the expected results: > > =========== > [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: > 4.875 sec =========== > > But, when I try "maven jcoverage", I get: > > ========== > [junit] Tests run: 6, Failures: 0, Errors: 6, Time elapsed: > 0.344 sec [junit] [ERROR] TEST <myclass> FAILED > > BUILD FAILED > File...... C:\Documents and > Settings\dhartford\.maven\cache\maven-test-plugin-1. > 6.2\plugin.jelly > Element... fail > Line...... 181 > Column.... 54 > There were test failures. > ========== I had the same issue once and it was caused by the fact that jcoverage writes a lot of log entries and my test expected some specific log output. - J�rg --------------------------------------------------------------------- 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]
