It's hardcoded in the plugin (and this is why you have things like sources:jar and sources:jar-no-fork depending on how you need/want to invoke it)
Le dim. 22 déc. 2019 à 18:04, Stanimir Stamenkov <s7a...@netscape.net.invalid> a écrit : > 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 > > -- > Stanimir > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
