What I am trying to say is that you can just add all these invocations to one profile and bind them to different phases or just the same phase and have them in order in the pom file and then you just invoke the one profile.
Plugin invocations can all be bound to specific phases in the pom and can be bound to a default phase in the code of the plugin. Manfred Stanimir Stamenkov wrote on 2019-12-24 08:47 (GMT -08:00): > Tue, 24 Dec 2019 17:27:18 +0100 (CET), /Manfred Moser/: > >> Typically a separate invocation like needing to update the data schema >> involves more than one plugin. >> >> The best and most common example is a release profile. It often includes >> things like javadoc, signing, obfustcating, creating additional files and so >> on. And you just run it with a profile. >> >> >> If you truly want to invoke only the one plugin, it wont matter. But in >> practice .. most of time it will be more than one plugin at a time. > > In my use case the (liquibase) maven plugin is only used for > development. The development of a new database change generally > involves multiple command invocations: > > # Prepare source change > mvn liquibase:update > mvn liquibase:rollback > # Update the change in the source, then > mvn liquibase:updateTestingRollback > > Rinse and repeat, and mix other goals into the cycle. This would happen > even if the plugin is otherwise programmed into a release profile. So > I've asked if it is possible to configure the default behavior to always > execute process-resources phase with this plugin, but seems it is > currently not. > > -- > Stanimir > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
