Mon, 23 Dec 2019 11:37:19 +0100, /Thomas Broyer/:
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)
I see now – thanks for clarifying. I've always wondered what those *-no-fork goals are for – I've thought it has to do something with forking the JVM process but seems I've been completely wrong. :-) In any case, I think dynamic "executePhase" configuration would be really nice to have, the same way one could dynamically bind a goal to a specific phase.
Le dim. 22 déc. 2019 à 18:04, Stanimir Stamenkov 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: [email protected] For additional commands, e-mail: [email protected]
