That would reconfigure which phase the mojo is bound to (if any, which is not the case if the Liquibase plugin) when executed as part of the build lifecycle; it won't allow you to fork a lifecycle when calling the goal directly.
Le lun. 23 déc. 2019 à 15:02, Mark Prins <[email protected]> a écrit : > You should be able to change the default execution phase of a plugin (as > well as bind a goal to any other phase) by configuring explicit > executions bound to a phase > > see: https://maven.apache.org/guides/mini/guide-default-execution-ids.html > > You would need to use an id of "default-update" to override the update > goal. > > -M > > > On 22-12-19 18:04, Stanimir Stamenkov wrote: > > I'm having a POM like: > > > > <build> > > <pluginManagement> > > <plugins> > > <plugin> > > <groupId>org.liquibase</groupId> > > <artifactId>liquibase-maven-plugin</artifactId> > > <version>3.8.3</version> > > <configuration> > > <changeLogFile>...</changeLogFile> > > </configuration> > > </plugin> > > </plugins> > > </pluginManagement> > > </build> > > > > I don't want the plugin executed as part of the build but I want to be > > able to execute its goals [1] explicitly. The goals get executed > > directly (no build phases get triggered), f.e.: > > > > mvn liquibase:update > > > > but then it usually (while not necessarily, depending on project > > configuration) require "process-resources" to be completed, so I have to: > > > > mvn process-resources liquibase:update > > > > Is it possible to trigger "process-resources" automatically via plugin > > configuration in POM (a`la Gradle's dependsOn [2]), or this is just > > hard-coded in the plugin itself? > > > > [1] https://www.liquibase.org/documentation/maven/index.html > > [2] https://docs.gradle.org/current/userguide/more_about_tasks.html > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
