This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git

commit da194240f94f910b02af54c3df1db87677e9039b
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Tue Nov 3 21:44:16 2026 +0100

    Say which later phases Maven 4 runs with compile and prepare-package
    
    Maven 4.0.0-rc-7 runs the goals bound to process-classes with
    mvn compile, and jar:jar with mvn prepare-package; Maven 3.9.16 and
    3.10.0 do neither.
---
 content/markdown/guides/introduction/introduction-to-the-lifecycle.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/content/markdown/guides/introduction/introduction-to-the-lifecycle.md 
b/content/markdown/guides/introduction/introduction-to-the-lifecycle.md
index fb4497ea..58f81cf6 100644
--- a/content/markdown/guides/introduction/introduction-to-the-lifecycle.md
+++ b/content/markdown/guides/introduction/introduction-to-the-lifecycle.md
@@ -103,7 +103,7 @@ Code coverage tools such as Jacoco and execution container 
plugins such as Tomca
 
 Failsafe and code coverage plugins bind goals to `integration-test` and 
`verify` phases. The net result is test and coverage reports are available 
after the `verify` phase. If `integration-test` were to be called from the 
command line, no reports are generated. Worse is that the integration test 
container environment is left in a hanging state; the Tomcat webserver or 
Docker instance is left running, and Maven may not even terminate by itself.
 
-This holds for Maven 3. Maven 4 gives every phase a `before:` and an `after:` 
phase, which take the place of the `pre-` and `post-` phases (bindings to the 
old names still work), and always runs both with the phase itself: `mvn 
integration-test` also runs the goals bound to `post-integration-test`. See 
[What's new in Maven 
4](../../whatsnewinmaven4.html#Before-_and_after-phases.2C_ordering_of_executions).
+This holds for Maven 3. Maven 4 gives every phase a `before:` and an `after:` 
phase, which take the place of the `pre-` and `post-` phases (bindings to the 
old names still work), and always runs both with the phase itself: `mvn 
integration-test` also runs the goals bound to `post-integration-test`. The 
same applies to other phases that follow one you call: `mvn compile` also runs 
the goals bound to `process-classes`, and in a `jar` project `mvn 
prepare-package` already runs `jar:jar` and [...]
 
 _[top](./introduction-to-the-lifecycle.html)._
 

Reply via email to