Executions are plugged into *prepare-package* and *install *phase so mvn clean install must work (in this example)
You can bind execution to differents phases to manage the right sequence but they are ordered into the same phase (I've already used it in another project without trouble) It's not mandatory to use it with profiles, you can just configure the sql-maven-plugin found in your build>plugins>plugin. In my case, I use a profile to launch the sql-maven-plugin only on the integration server which will activate this profile. Here you have the default phase ordered validateinitializegenerate-sourcesprocess-sourcesgenerate-resources process-resourcescompileprocess-classesgenerate-test-sources process-test-sourcesgenerate-test-resourcesprocess-test-resources test-compileprocess-test-classestestprepare-packagepackage pre-integration-testintegration-testpost-integration-testverifyinstalldeploy You should read this to undestranad Maven lifecycle http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html Lifecycle>phases>goals 2012/2/6 Ilia Ternovich <[email protected]> > Hi Sebastien! > > How do you launch it? How do you specify that drop-db is performed > before create-db? > > Thanks! > -- ------------------------------------------------------------------------------- [email protected] - http://www.webeo.fr
