(maven-site) branch elharo-patch-1 created (now 400ae3f6)

[el...@apache.org]

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

elharo pushed a change to branch elharo-patch-1
in repository https://gitbox.apache.org/repos/asf/maven-site.git


      at 400ae3f6 [MNGSITE-393] Remove Maven 2.0 content

This branch includes the following new commits:

     new 400ae3f6 [MNGSITE-393] Remove Maven 2.0 content

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

(maven-site) 01/01: [MNGSITE-393] Remove Maven 2.0 content

[el...@apache.org]

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

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

commit 400ae3f67a6d86889592c11faa96050d32f0812d
Author: Elliotte Rusty Harold <el...@users.noreply.github.com>
AuthorDate: Mon Oct 21 15:11:54 2024 +0000

    [MNGSITE-393] Remove Maven 2.0 content
    
    and some other minor copy edits
---
 .../guides/introduction/introduction-to-the-lifecycle.apt    | 12 +++++-------
 1 file changed, 5 insertions(+), 7 deletions(-)

diff --git a/content/apt/guides/introduction/introduction-to-the-lifecycle.apt b/content/apt/guides/introduction/introduction-to-the-lifecycle.apt
index 81b903b1..cd11f046 100644
--- a/content/apt/guides/introduction/introduction-to-the-lifecycle.apt
+++ b/content/apt/guides/introduction/introduction-to-the-lifecycle.apt
@@ -100,9 +100,9 @@ mvn verify
 
   This command executes each default lifecycle phase in order (<<<validate>>>, <<<compile>>>, <<<package>>>, etc.), 
   before executing <<<verify>>>.  You only need to call the last build phase to be executed, in this case, <<<verify>>>.
-  In most cases the effect is the same as <<<package>>>. However, in case there are integration-tests, these will be
-  executed as well. And during the <<<verify>>> phase some additional checks can be done, e.g. if your code written
-  according to the predefined checkstyle rules.
+  In most cases the effect is the same as <<<package>>>. However, in case there are integration tests, these will be
+  executed as well. And during the <<<verify>>> phase additional checks can be done, e.g. if your is code written
+  according to predefined checkstyle rules.
 
   In a build environment, use the following call to cleanly build and deploy artifacts into the shared repository.
 
@@ -140,10 +140,8 @@ mvn clean dependency:copy-dependencies package
   Furthermore, a build phase can also have zero or more goals bound to it. If a build phase has no goals bound to it,
   that build phase will not execute. But if it has one or more goals bound to it, it will execute all those goals.
 ~~~
-~~~ Check if the following is true for Maven 3...
-  (<Note: In Maven 2.0.5 and above, multiple goals bound to a phase are executed in the same order as they are declared in the
-  POM, however multiple instances of the same plugin are not supported. Multiple instances of the same plugin are grouped to execute together and ordered in
-  Maven 2.0.11 and above>).
+  Multiple goals bound to a phase are executed in the same order as they are declared in the
+  POM. Multiple instances of the same plugin are grouped to execute together.
 ~~~
 
   <{{{./introduction-to-the-lifecycle.html}[top]}}.>