An alternative is to use a properties file in <configuration>...</configuration> and define one profile for each database configuration to apply it at the plugin's execution.
So you can select the profile corresponding to the db and the changelog associated at the execution of the plugin.
Send me your full configuration of pom.xml by PV if you are interested by this alternative because i haven't the time at this moment to post the few steps.
Regards
So you can select the profile corresponding to the db and the changelog associated at the execution of the plugin.
Send me your full configuration of pom.xml by PV if you are interested by this alternative because i haven't the time at this moment to post the few steps.
Regards