Other plugins starting when running dbm-status dbm-update....

[jglapa]

I've run into a situation where I couldn't execute a schema update process.
I'm using quartz plugin and I wanted to use the job persistence feature which required DB tables that are included into changelog. What happened is: while executing dbm-status or dbm-update quartz plugin started looking for the DB tables that were not created yet and failed. I had to manually disable the plugin to run the update process.

This is also a problem when you use rabbitmq plugin, all the listeners start connecting when you run a dbm task. I would expect that nothing else starts when I'm running those kind of tasks.

So the question is: Is it possible to control the order in which the plugins are starting? What would be a different approach to fix the problem? Most of the plugin have a disable property, could the dbm plugin use them if we would specify that when dbm task runs please set to those properties to false?

I would be willing to contribute but somebody would have to point me into the right direction.