Hi, just uploaded the patch to
http://jira.codehaus.org/browse/CASTOR-2671 Cheers Werner Werner Guttmann wrote: > Hi, > > I spent a few hours in the last few days to start adding profiles to the > CPACTF so that the following things are possible by default: > > a) Execution of the test suite for a given database (e.g. Derby, mySQL, > Oracle, ....) by invoking a Maven profile (mvn -P mysql clean test). > b) Addition of a default profile that will be executed if no other > profile is specified. This is required for our continuous integration > definitions, and will default to Derby (embedded). > > I have some changes to the Maven POM ready to review/commit, and I am in > the position to run the CPA test suite both against Derby and mySQL > using Maven profiles. > > Here's a few reasons why I initially started to work on this: > > Benefit a) I wanted complete automation of the database setup through > Maven, and its sql-maven-plugin. In other words, no more manual > interactions required. > Benefit b) I wanted profile-specific declaration of JDBC driver > dependencies, rather than having to use the <optional>true</optional> > property again and again. > Benefit c) I wanted to avoid having to edit cpactf-conf.xml for testing > with different databases. > > I will create a Jira issue later on today, and attach things to review. > > Whilst working on this patch, though, I came across a few things I'd > like to change: > > 1) Can we please use 'qualified' system property names in CPATestCase, > i.e. "org.castor.cpa.ctf.database" rather than just "database", to avoid > any ambiguity ? > 2) Can we please break apart cpactf-conf.xml into smaller, > database-specific JDO config files, i.e. (re)start having mysql-drv.xml, > derby-embedded.xml, etc. again ? > > Any objections ? If not, let me include those changes with an update to > the original patch later on. > > Cheers > Werner > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
