Investigate why entitymanager test cannot be run in forkMode once ----------------------------------------------------------------- Key: HHH-4845 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4845 Project: Hibernate Core Issue Type: Bug Components: build, entity-manager Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.5 Currently the forkMode for the entitymanager module is once. To improve the build speed it would be nice to only fork once. However, forking once triggers some test failures. The initial thought was that the tests which rely on packages (war, par, etc ...) cause the problem. A solution for this could be http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing Looking at the actual failing tests might indicate another problem though. The failing tests are: {code} Failed tests: testCreateExceptionWithGeneratedId(org.hibernate.ejb.test.ops.PersistTest) Tests in error: testFlushOnDetached(org.hibernate.ejb.test.emops.FlushTest) testSerialization(org.hibernate.ejb.test.ejb3configuration.EntityManagerSerializationTest) Tests run: 182, Failures: 1, Errors: 2, Skipped: 0 {code} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira