3 ms·
"It's gotten a lot better because there are many examples now accessible with Google." That is the main reason I am sticking with Maven (where practical). Exam
by oftenwrong 9y ago
"It's gotten a lot better because there are many examples now accessible with Google."
That is the main reason I am sticking with Maven (where practical). Examples, documentation, and answered questions are plentiful.
"Configuring plugins to fire at the right point in the build cycle (e.g., package vs. install) comes lightly to mind."
The official documentation has that covered well: https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html https://maven.apache.org/guides/introduction/introduction-to...
An example they give is:
...
<plugin>
<groupId>com.mycompany.example</groupId>
<artifactId>display-maven-plugin</artifactId>
<version>1.0</version>
<executions>
<execution>
<phase>process-test-resources</phase>
<goals>
<goal>time</goal>
</goals>
</execution>
</executions>
</plugin>
...
i.e. plugin "display-maven-plugin" should execute its "time" goal during the "process-test-resources" phase.
IIUC, there are no fixed phases in Gradle, so this sort of thing is done with task dependencies.