topic Grails DB migrations in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/grails-db-migrations/m-p/165776#M119437 <HTML><HEAD></HEAD><BODY><SPAN>We picked up the sql files from activiti jar to create the tables, but the team's getting annoyed to do the manual drop-create every time they need reset the base, so I was instructed to configure the auto-migrations in our grails project, but no matter which way I do it, activiti looks for the base before migrations runs, I'd tried to configure migrations to run sql, I'd tried to generate changelog from a healthy cleaned database, but every time I run the project it claims for the ACT_GE_PROPERTY table which runs a SELECT.</SPAN><BR /><BR /><SPAN>How an I make activiti runs after Grails DB migrations, or make activiti drop-create the base correctly?</SPAN><BR /><BR /><SPAN>Thanks,</SPAN></BODY></HTML> Thu, 19 Sep 2013 13:31:41 GMT chewbacca 2013-09-19T13:31:41Z Grails DB migrations https://connect.hyland.com/t5/alfresco-archive/grails-db-migrations/m-p/165776#M119437 We picked up the sql files from activiti jar to create the tables, but the team's getting annoyed to do the manual drop-create every time they need reset the base, so I was instructed to configure the auto-migrations in our grails project, but no matter which way I do it, activiti looks for the base Thu, 19 Sep 2013 13:31:41 GMT https://connect.hyland.com/t5/alfresco-archive/grails-db-migrations/m-p/165776#M119437 chewbacca 2013-09-19T13:31:41Z Re: Grails DB migrations https://connect.hyland.com/t5/alfresco-archive/grails-db-migrations/m-p/165777#M119438 <HTML><HEAD></HEAD><BODY><SPAN>I solved the problem setting deploymentResources to null, then processEngine doesn't require the base, then migrations works, however it requires processEngineConfiguration.autoDeployResources(processEngine) to be called on BootStrap after restore the original deploymentResources!</SPAN><BR /><BR /><SPAN>Something like that on BootStrap.init:</SPAN><BR /><SPAN>&lt;code&gt;grailsApplication.config.activiti.deploymentResources = grailsApplication.config.activiti.deploymentResourcesBackup</SPAN><BR /><SPAN>def resolver = new PathMatchingResourcePatternResolver(grailsApplication.mainContext)</SPAN><BR /><SPAN>def resources = []</SPAN><BR /><SPAN>grailsApplication.config.activiti.deploymentResources.each { deployResource -&gt;</SPAN><BR /><SPAN> resources.addAll(resolver.getResources(deployResource))</SPAN><BR /><SPAN>}</SPAN><BR /><SPAN>processEngineConfiguration.setDeploymentResources(resources.toArray(new Resource[resources.size]))</SPAN><BR /><SPAN>processEngineConfiguration.autoDeployResources(processEngine)&lt;/code&gt;</SPAN></BODY></HTML> Thu, 19 Sep 2013 20:46:29 GMT https://connect.hyland.com/t5/alfresco-archive/grails-db-migrations/m-p/165777#M119438 chewbacca 2013-09-19T20:46:29Z