This is an automated email from the ASF dual-hosted git repository.
elharo pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new 6b8407c8 [MNGSITE-393] Remove Maven 2.0 content (#565)
6b8407c8 is described below
commit 6b8407c821deef86f7dc68ad349b1cd0bb7ce8ec
Author: Elliotte Rusty Harold <elh...@users.noreply.github.com>
AuthorDate: Thu Oct 24 20:37:34 2024 +0000
[MNGSITE-393] Remove Maven 2.0 content (#565)
* [MNGSITE-393] Remove Maven 2.0 content
and some other minor copy edits
* Update introduction-to-the-lifecycle.apt
---
.../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..5f7b78c6 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 code is 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]}}.>
