Thanks for the tips! That helped me to idenitfy the failing unit tests.
I now figured out that there are tests in cpm, which only fail with
mvn test
but not with
mvn install
The failing tests are: Test set: org.apache.uima.collection.impl.CollectionProcessingEngine_implTest Test set: org.apache.uima.collection.impl.cpm.SofaCPE_SofaUnawareCC_Test Test set: org.apache.uima.collection.impl.cpm.SofaCPE_Test Test set: org.apache.uima.collection.impl.cpm.SofaMixedCPE_Test These tests are fine when tested in Eclipse (here the testcase org.apache.uima.collection.impl.cpm.CpmCollectionReader_ErrorTests#testHasNextWithOutOfMemoryErrorfails). Any suggestions, what I might be doing wrong? I thought, "mvn install" refers to "mvn test", so it shouldn't create different results. BTW, right now I am using the latest Java Version available for Mac: java version "1.5.0_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-112) Java HotSpot(TM) Client VM (build 1.5.0_06-64, mixed mode, sharing) -- Mirko On 1/16/07, Adam Lally <[EMAIL PROTECTED]> wrote:
On 1/16/07, Marshall Schor <[EMAIL PROTECTED]> wrote: > I install Eclipse on the Mac; then I checkout the projects to Eclipse; > then run the build; > then use Eclipse Search -> File, over the whole workspace, for files of > *.xml, looking for the string > <<< FAILURE! > I do a grep (case senstive) for "FAILURE" in the target/surefire-reports directory of the component whose build test failed. (Usually you can tell which test case failed by the last few lines of test output.) But then to actually debug the test I run it in Eclipse. BTW, be sure you update from SVN, I fixed several unit tests problems yesterday. There are also a few new JIRA issues open relating to failures in Sun Java 1.4 (and I see today, 1.6), so you may want to use a different Java for now. -Adam
