[ https://jira.jboss.org/jira/browse/JBPM-1718?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1718: --------------------------------- Description: (was: <excludes> <exclude>org/jbpm/persistence/db/PersistenceServiceDbTest.java</exclude> <exclude>org/jbpm/persistence/db/PersistenceServiceFactoryDbTest.java</exclude> </excludes> ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-1718?page=com.atlassian.jira.plug... ] Thomas Diesler commented on JBPM-1718: -------------------------------------- Alejandro sais, It ain't configuration, it is the AbstractDbTestCase code: http://anonsvn.jboss.org/repos/jbpm/jbpm3/trunk/modules/core/src/main/jav... Code: public void setUp() throws Exception { createSchema(); // HERE createJbpmContext(); initializeMembers(); } public void tearDown() throws Exception { resetMembers(); closeJbpmContext(); dropSchema(); // AND HERE super.tearDown(); } Note however that removing the above lines will be a challenge because many tests depend on an empty database. Perhaps we could simply clear the tables instead of dropping them? Of course that would imply caring about constraint violations. Not an easy way out either. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-1718?page=com.atlassian.jira.plug... ] Work on JBPM-1718 started by Thomas Diesler. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-1718?page=com.atlassian.jira.plug... ] Thomas Diesler commented on JBPM-1718: -------------------------------------- Did some refactoring and removed the dropSchema() call in tearDown(); [tdiesler@tdvaio core]$ mvn -o -Ddatabase=postgresql test ... Tests run: 982, Failures: 0, Errors: 0, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 9 minutes 37 seconds [INFO] Finished at: Fri Sep 12 01:10:25 CEST 2008 [INFO] Final Memory: 11M/42M [INFO] ------------------------------------------------------------------------ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-1718?page=com.atlassian.jira.plug... ] Tom Baeyens commented on JBPM-1718: ----------------------------------- at some point i introduced cleaning of the DB based on clearing the tables (delete from table-name). this was surrounded with dropping and recreating the foreign key constraints. it worked fine. i have no clue why it was changed back to dropping the whole dbs inbetween all the tests. in case i did it myself, i don't remember the reason. in jBPM 4 we now use the clearing code that i developed in 3 to clear the tables. it works there as well. so it could be considered to reintroduce that code in jbpm 3. here is the code to clean the DB instead of dropping and recreating it: http://fisheye.jboss.com/browse/~raw,r=1871/JbpmSvn/jbpm4/pvm/trunk/modul... it might be worthed to give that a try -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-1718?page=com.atlassian.jira.plug... ] Work on JBPM-1718 started by Thomas Diesler. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-1718?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1718: --------------------------------- Summary: [WoD] Pass testsuite against postgresql (was: Pass testsuite against postgresql) Waiting for dependent issues to be completed -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-1718?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1718: --------------------------------- Comment: was deleted -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-1718?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1718: --------------------------------- Summary: Pass testsuite against postgresql (was: [WoD] Pass testsuite against postgresql) Labels: WoD (was: ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira