I like the idea of maven profiles that will allow to execute cpactf through maven against different databases. There are only 3 points I do not like much at the current patch which uses maven-sql-plugin to setup database:
1. You have to add connection information for every database in pom.xml and cpactf-conf.xml. And they have to be in sync to execute tests successfully.
2. You have to add <srcFile>...</srcFile> definition in pom.xml for every database engine and every test. As we support 11 database engines and have about 85 tests this will lead us to around 1000 such definitions in pom.xml. In my opinon it will be a nightmare to maintain them. Not to forget the length of the rest of the profil definitions.
3. As mentioned when we introduced maven target to execute against embedded derby, we are still not able to execute/debug cpactf tests against this database engine within eclipse.
At http://jira.codehaus.org/browse/CASTOR-2650 I like to address this 3 issues. Therefore I would appreciate if you could wait for some time to let me finish my work on this issue. I am quite confident that this will make support for maven profiles for cpactf much simpler.
Initial patch for review. To execute test suite for ...., please issue:
Note: I still have to add one more sql-maven-plugin execution to automate database creation.