We do this in our internal maven 1.x 'db' plugin. We have goals like:
db:create db:create-schema db:drop-schema db:delete db:clean db:load-dataset db:unload-dataset etc... On 8/8/07, Eric Redmond <[EMAIL PROTECTED] > wrote: > > This may be a good suggestion for JIRA. I am not against the addition of a > > database lifecycle, since it is a valid case. Though some may claim it is > a > slippery slope - I have suggested a release lifecycle for similar > arguments... it is something you do occasionally (like "clean" or "site") > but is common enough to standardize. > > -- > Eric Redmond > http://blog.propellors.net > > On 8/4/07, Victor Bendig <[EMAIL PROTECTED] > wrote: > > > > Hi, > > > > Have a couple of questions around databases and maven, > > > > 1. Does Maven create standards for database development? > > 2. Is there a plugin that handles the lifecycle of the database (create, > > > drop, etc) > > > > I found a sql-maven-plugin but this forces me to bind sql files to code > > phases. While this might be good when testing, I find it might be heavy > > if > > I bind the install of my project with the database creation. > > > > Any ideas where I can look for this? > > > > Regards, > > > > > > -- > > Victor Bendig > > > -- dIon Gillard Rule #131 of Acquisition: Information is Profit.
