You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by el...@apache.org on 2026/08/03 18:52:06 UTC
(maven-antrun-plugin) branch docs/ste100-site-rewrite created (now 33e6a6e)
This is an automated email from the ASF dual-hosted git repository.
elharo pushed a change to branch docs/ste100-site-rewrite
in repository https://gitbox.apache.org/repos/asf/maven-antrun-plugin.git
at 33e6a6e Rewrite site documentation in Simplified Technical English
This branch includes the following new commits:
new 33e6a6e Rewrite site documentation in Simplified Technical English
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-antrun-plugin) 01/01: Rewrite site documentation in Simplified Technical English
Posted by el...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
elharo pushed a commit to branch docs/ste100-site-rewrite
in repository https://gitbox.apache.org/repos/asf/maven-antrun-plugin.git
commit 33e6a6e02dbd68f08f7fb5615289419f02aadcf7
Author: Elliotte Rusty Harold <el...@ibiblio.org>
AuthorDate: Mon Aug 3 18:51:55 2026 +0000
Rewrite site documentation in Simplified Technical English
---
src/site/apt/examples/classpaths.apt.vm | 33 ++++++++--------
src/site/apt/examples/customTasks.apt.vm | 7 ++--
src/site/apt/examples/tasksAttributes.apt.vm | 5 ++-
src/site/apt/index.apt.vm | 58 ++++++++++++----------------
src/site/apt/tasks/attachArtifact.apt.vm | 10 ++---
src/site/apt/tasks/dependencyFilesets.apt.vm | 26 +++++++------
src/site/apt/tasks/tasks.apt.vm | 11 +++---
src/site/apt/tasks/versionMapper.apt.vm | 5 +--
src/site/apt/usage.apt.vm | 43 +++++++++------------
src/site/fml/faq.fml | 13 +++----
src/site/xdoc/download.xml.vm | 15 ++++---
11 files changed, 107 insertions(+), 119 deletions(-)
diff --git a/src/site/apt/examples/classpaths.apt.vm b/src/site/apt/examples/classpaths.apt.vm
index 0d1c6e5..c3a4035 100644
--- a/src/site/apt/examples/classpaths.apt.vm
+++ b/src/site/apt/examples/classpaths.apt.vm
@@ -28,27 +28,30 @@
Referencing the Maven Classpaths
- A property is set in the Ant build for each project dependency. Each property name uses the format
- <<groupId:artifactId:type[:classifier]>>. For example, to show the path to a
- jar dependency with groupId "org.apache" and artifactId "common-util", the following could be used.
+ The plugin sets a property in the Ant build for each project dependency.
+ Each property name uses the format <<groupId:artifactId:type[:classifier]>>.
+
+ To show the path to a jar dependency with groupId "org.apache" and
+ artifactId "common-util", use this:
+---+
#set( $D = '$' )
<echo message="${D}{org.apache:common-util:jar}"/>
+---+
- If the dependency includes a classifier, the classifier is appended to the property name.
- For example, groupId "org.apache", artifactId "common-util", type "jar", and classifier "jdk14".
-
+ If the dependency includes a classifier, the plugin appends the classifier
+ to the property name. For example, groupId "org.apache", artifactId
+ "common-util", type "jar", and classifier "jdk14":
+
+---+
#set( $D = '$' )
<echo message="${D}{org.apache:common-util:jar:jdk14}"/>
+---+
- <<Note:>> the old format "maven.dependency.groupId.artifactId[.classifier].type.path" is not supported as of version
- 3.0.0 of the plugin.
-
- You can also use these classpath references:
+ <<Note:>> the old format <<maven.dependency.groupId.artifactId[.classifier].type.path>> is not supported
+ in version 3.0.0 of the plugin.
+
+ You can also use these classpath references:
* <<<maven.compile.classpath>>>
@@ -57,9 +60,7 @@ Referencing the Maven Classpaths
* <<<maven.test.classpath>>>
* <<<maven.plugin.classpath>>>
-
-
- For example, to display Maven's classpaths using antrun, we can do this
+ To display Maven's classpaths with antrun, use this:
+---+
<project>
@@ -104,7 +105,7 @@ Referencing the Maven Classpaths
+---+
- or alternatively, we can use an external <<<build.xml>>>.
+ Or use an external <<<build.xml>>>:
+---+
<project>
@@ -147,7 +148,7 @@ Referencing the Maven Classpaths
</project>
+---+
- The <<<build.xml>>>:
+ The <<<build.xml>>>:
+---+
<?xml version="1.0"?>
@@ -163,4 +164,4 @@ Referencing the Maven Classpaths
</target>
</project>
-+---+
\ No newline at end of file
++---+
diff --git a/src/site/apt/examples/customTasks.apt.vm b/src/site/apt/examples/customTasks.apt.vm
index f3ca0b7..22c070c 100644
--- a/src/site/apt/examples/customTasks.apt.vm
+++ b/src/site/apt/examples/customTasks.apt.vm
@@ -28,8 +28,9 @@
Using tasks not included in Ant's default jar
- To use Ant tasks not included in the Ant jar, like Ant optional or custom tasks you need to add the dependencies needed for the task
- to run to the plugin classpath and use the <<<maven.plugin.classpath>>> reference if needed.
+ To use Ant tasks that are not in the Ant jar, add the task dependencies to
+ the plugin classpath. Use the <<<maven.plugin.classpath>>> reference if
+ needed.
+---+
<project>
@@ -80,7 +81,7 @@ Using tasks not included in Ant's default jar
</project>
+---+
- Another example of this is the use of {{{http://ant-contrib.sourceforge.net/}Ant-Contrib}} tasks:
+ Another example uses the {{{http://ant-contrib.sourceforge.net/}Ant-Contrib}} tasks:
+---+
<project>
diff --git a/src/site/apt/examples/tasksAttributes.apt.vm b/src/site/apt/examples/tasksAttributes.apt.vm
index 12241ab..87adc20 100644
--- a/src/site/apt/examples/tasksAttributes.apt.vm
+++ b/src/site/apt/examples/tasksAttributes.apt.vm
@@ -28,8 +28,9 @@
Using <<<\<target/\>>>> Attributes
- You can specify attributes in the <<<\<target/\>>>> configuration to execute or not Ant tasks
- depending some conditions. For example, to skip Ant call, you could add the following:
+ You can use attributes in the <<<\<target/\>>>> configuration to run or skip
+ Ant tasks. The attributes depend on conditions. To skip the Ant call, add
+ this:
+---+
<project>
diff --git a/src/site/apt/index.apt.vm b/src/site/apt/index.apt.vm
index 1e2a85a..41eb551 100644
--- a/src/site/apt/index.apt.vm
+++ b/src/site/apt/index.apt.vm
@@ -28,18 +28,16 @@
${project.name}
- This plugin provides the ability to run Ant tasks from within Maven. You can
- even embed your Ant scripts in the POM!
+ This plugin runs Ant tasks from inside Maven. You can embed your Ant
+ scripts in the POM.
- It is <not> the intention of this plugin to provide a means of polluting the
- POM, so it's encouraged to move all your Ant tasks to a <<<build.xml>>> file
- and just call it from the POM using Ant's
- {{{https://ant.apache.org/manual/Tasks/ant.html}\<ant/\> task}}.
+ This plugin does not intend to fill the POM with your Ant tasks. Move all
+ your Ant tasks to a <<<build.xml>>> file. Call the file from the POM with
+ Ant's {{{https://ant.apache.org/manual/Tasks/ant.html}\<ant/\> task}}.
- One of the main purposes of this plugin is to facilitate the migration from Ant
- based projects to Maven. Some projects may not currently be able to migrate
- because they depend on custom build functionality that Maven doesn't provide
- by default.
+ A main purpose of this plugin is to help projects migrate from Ant to
+ Maven. Some projects depend on custom build functions that Maven does not
+ provide by default. These projects cannot migrate yet.
* Goals Overview
@@ -47,45 +45,39 @@ ${project.name}
* Major Version Upgrade to version 3.0.0
- Please note that the following parameters have been completely removed from the plugin configuration:
+ The following parameters are removed from the plugin configuration:
- * <<<tasks>>>: use <<<target>>> instead;
+ * <<<tasks>>>: use <<<target>>> instead.
- * <<<sourceRoot>>> and <<<testSourceRoot>>>: you can use the
- {{{https://www.mojohaus.org/build-helper-maven-plugin/}build-helper-maven-plugin}} instead, with its
+ * <<<sourceRoot>>> and <<<testSourceRoot>>>: use the
+ {{{https://www.mojohaus.org/build-helper-maven-plugin/}build-helper-maven-plugin}} instead. Use its
{{{https://www.mojohaus.org/build-helper-maven-plugin/add-source-mojo.html}add-source}} and
{{{https://www.mojohaus.org/build-helper-maven-plugin/add-test-source-mojo.html}add-test-source}} goals.
- The format <<<maven.dependency.groupId.artifactId[.classifier].type.path>>> to reference the path of a project
- dependency as an Ant property has been removed: use <<<groupId:artifactId:type[:classifier]>>> instead.
+ The format <<<maven.dependency.groupId.artifactId[.classifier].type.path>>> no longer references the path of a
+ project dependency as an Ant property. Use <<<groupId:artifactId:type[:classifier]>>> instead.
* Usage
- General instructions on how to use the AntRun Plugin can be found on the {{{./usage.html}usage page}}. Some more
- specific use cases are described in the examples given below.
+ The {{{./usage.html}usage page}} contains general instructions for the AntRun Plugin. The examples below
+ describe specific use cases.
- In case you still have questions regarding the plugin's usage, please have a look at the {{{./faq.html}FAQ}} and feel
- free to contact the {{{./mailing-lists.html}user mailing list}}. The posts to the mailing list are archived and could
- already contain the answer to your question as part of an older thread. Hence, it is also worth browsing/searching
- the {{{./mailing-lists.html}mail archive}}.
+ If you have questions about the plugin, read the {{{./faq.html}FAQ}}. Contact the
+ {{{./mailing-lists.html}user mailing list}}. The mailing list posts are archived. An older thread can
+ contain the answer to your question. Browse the {{{./mailing-lists.html}mail archive}}.
- If you feel like the plugin is missing a feature or has a defect, you can fill a feature request or bug report in our
- {{{./issue-management.html}issue tracker}}. When creating a new issue, please provide a comprehensive description of your
- concern. Especially for fixing bugs it is crucial that the developers can reproduce your problem. For this reason,
- entire debug logs, POMs or most preferably little demo projects attached to the issue are very much appreciated.
- Of course, patches are welcome, too. Contributors can check out the project from our
- {{{./scm.html}source repository}} and will find supplementary information in the
- {{{/guides/development/guide-helping.html}guide to helping with Maven}}.
+ If the plugin misses a feature or has a defect, report it in the {{{./issue-management.html}issue tracker}}.
+ Describe the issue in detail. The developers must reproduce your problem to fix a bug. Attach debug logs,
+ POMs, or a small demo project to the issue. Patches are welcome. Get the project from the
+ {{{./scm.html}source repository}}. Read the {{{/guides/development/guide-helping.html}guide to helping with Maven}}
+ for more information.
* Examples
- To provide you with better understanding on some usages of the Maven AntRun
- Plugin, you can take a look into the following examples:
+ These examples show how to use the Maven AntRun Plugin:
* {{{./examples/classpaths.html}Referencing the Maven Classpaths}}
* {{{./examples/tasksAttributes.html}Using <<<\<target/\>>>> Attributes}}
* {{{./examples/customTasks.html}Using tasks not included in Ant's default jar}}
-
- []
diff --git a/src/site/apt/tasks/attachArtifact.apt.vm b/src/site/apt/tasks/attachArtifact.apt.vm
index 29a08da..593242a 100644
--- a/src/site/apt/tasks/attachArtifact.apt.vm
+++ b/src/site/apt/tasks/attachArtifact.apt.vm
@@ -28,8 +28,8 @@
AttachArtifact Task
- This task will attatch an artifact to the current Maven project. This is can be used to install and
- deploy an artifact generated by the Ant tasks.
+ This task attaches an artifact to the current Maven project. Use the task
+ to install and deploy an artifact that the Ant tasks generate.
* Task Parameters
@@ -38,9 +38,9 @@ AttachArtifact Task
*---------------+--------------------------------------------------------+-----------------------------------*
| file | The file to attach to the project | Yes |
*---------------+--------------------------------------------------------+-----------------------------------*
-| classifier | A classifier assigned to the artifact | No, defaults to no classifier |
+| classifier | The classifier assigned to the artifact | No. Defaults to no classifier |
*---------------+--------------------------------------------------------+-----------------------------------*
-| type | The type of the artifact, zip, war, etc | No, defaults to jar |
+| type | The type of the artifact, zip, war, etc | No. Defaults to jar |
*---------------+--------------------------------------------------------+-----------------------------------*
@@ -72,4 +72,4 @@ AttachArtifact Task
</execution>
</executions>
</plugin>
-+---+
\ No newline at end of file
++---+
diff --git a/src/site/apt/tasks/dependencyFilesets.apt.vm b/src/site/apt/tasks/dependencyFilesets.apt.vm
index 14cec67..55818d7 100644
--- a/src/site/apt/tasks/dependencyFilesets.apt.vm
+++ b/src/site/apt/tasks/dependencyFilesets.apt.vm
@@ -28,32 +28,35 @@
DependencyFilesets Task
- This task will create fileset objects containing the Maven project dependencies. This can be used access
- specific dependency artifacts, or to operate on a set of dependency artifacts. Each artifact will be assigned
- a fileset ID in the form <<<[prefix]groupId:artifactId:[classifier]:type>>>. A dependency on a junit jar would be
- given a fileset ID of <<<junit:junit:jar>>>.
+ This task creates fileset objects that contain the Maven project
+ dependencies. You can use the task to access a specific dependency
+ artifact. You can also use the task to operate on a set of dependency
+ artifacts. Each artifact gets a fileset ID in the form
+ <<<[prefix]groupId:artifactId:[classifier]:type>>>. A junit jar dependency
+ gets the fileset ID <<<junit:junit:jar>>>.
- In addition, a single fileset containing all the project dependencies will be created using the default ID
- maven.project.dependencies
+ The task also creates a fileset with all the project dependencies. The
+ fileset uses the default ID maven.project.dependencies.
* Task Parameters
*---------------+--------------------------------------------------------+-----------------------------------*
|| Attribute || Description || Required |
*---------------+--------------------------------------------------------+-----------------------------------*
-| prefix | String to prepend to all fileset IDs | No, defaults to empty string |
+| prefix | String to prepend to all fileset IDs | No. Defaults to empty string |
*---------------+--------------------------------------------------------+-----------------------------------*
-| projectDependenciesId | RefId for the fileset containing all project dependencies | No, defaults to "maven.project.dependencies |
+| projectDependenciesId | RefId for the fileset with all project dependencies | No. Defaults to maven.project.dependencies |
*---------------+--------------------------------------------------------+-----------------------------------*
-| scopes | Comma separated list of artifact scopes to include | No, defaults to all artifacts |
+| scopes | Comma separated list of artifact scopes to include | No. Defaults to all artifacts |
*---------------+--------------------------------------------------------+-----------------------------------*
-| types | Comma separated list of artifact types to include | No, defaults to all artifacts |
+| types | Comma separated list of artifact types to include | No. Defaults to all artifacts |
*---------------+--------------------------------------------------------+-----------------------------------*
* Example
- This example shows how to access individual dependencies and the combined dependency fileset.
+ This example shows how to access individual dependencies and the combined
+ dependency fileset.
+---+
<plugin>
@@ -88,4 +91,3 @@ DependencyFilesets Task
</executions>
</plugin>
+---+
-
diff --git a/src/site/apt/tasks/tasks.apt.vm b/src/site/apt/tasks/tasks.apt.vm
index 8f8bf6c..fd92e17 100644
--- a/src/site/apt/tasks/tasks.apt.vm
+++ b/src/site/apt/tasks/tasks.apt.vm
@@ -28,17 +28,16 @@
Ant Tasks
- The Maven Antrun Plugin includes some custom Ant tasks which can be used to better integrate with the
- Maven build. This page provides an overview of these tasks. Click on the task name for more information
- and examples.
+ The Maven Antrun Plugin includes custom Ant tasks. The tasks improve the
+ integration with the Maven build. This page lists the tasks. Click a task
+ name for more information and examples.
*-----------------------------------------------------+--------------------------------------------------------+
|| Task || Description |
*---------------+--------------------------------------------------------+
| {{{./attachArtifact.html}attachartifact}} | Attach an artifact to the current Maven project |
*---------------+--------------------------------------------------------+
-| {{{./dependencyFilesets.html}dependencyfilesets}} | Creates a fileset for each of the Maven project dependencies and adds them to the Ant build |
+| {{{./dependencyFilesets.html}dependencyfilesets}} | Creates a fileset for each Maven project dependency and adds the filesets to the Ant build |
*---------------+--------------------------------------------------------+
-| {{{./versionMapper.html}versionMapper}} | Mapper to remove version from artifact filenames |
+| {{{./versionMapper.html}versionMapper}} | Removes the version from artifact filenames |
*---------------+--------------------------------------------------------+
-
\ No newline at end of file
diff --git a/src/site/apt/tasks/versionMapper.apt.vm b/src/site/apt/tasks/versionMapper.apt.vm
index da573cc..ee183f6 100644
--- a/src/site/apt/tasks/versionMapper.apt.vm
+++ b/src/site/apt/tasks/versionMapper.apt.vm
@@ -28,8 +28,8 @@
VersionMapper
- This is an Ant mapper class which can be used to remove the versions from the dependency
- artifact filenames..
+ This is an Ant mapper. The mapper removes the version from a dependency
+ artifact filename.
* Example
@@ -66,4 +66,3 @@ VersionMapper
</plugin>
+---+
-
diff --git a/src/site/apt/usage.apt.vm b/src/site/apt/usage.apt.vm
index e1d7ea0..613682e 100644
--- a/src/site/apt/usage.apt.vm
+++ b/src/site/apt/usage.apt.vm
@@ -32,10 +32,9 @@ Usage
The maven-antrun-plugin has only one goal, <<<run>>>.
- This allows Maven to run Ant tasks. To do so, there must be an existing
- project and maven-antrun-plugin must have its <<<\<target\>>>> tag
- configured (although it would still execute without the <<<\<target\>>>> tag,
- it would not do anything). Below is the template for
+ This goal lets Maven run Ant tasks. You need an existing project. The
+ plugin must have its <<<\<target\>>>> tag configured. Without this tag,
+ the plugin executes but does nothing. Below is the template for
<<<maven-antrun-plugin>>>'s <<<pom.xml>>>.
+---+
@@ -72,11 +71,11 @@ Usage
</project>
+---+
- Moreover, you can add a script to each lifecycle phase, by duplicating the
- <<<\<execution/\>>>> section and specifying a new phase.
+ You can add a script to each lifecycle phase. Duplicate the
+ <<<\<execution/\>>>> section. Specify a new phase in each copy.
- Ultimately, you could specify some Ant {{{http://ant.apache.org/manual/using.html#targets}<<<\<target/\>>>>}}
- attributes in the <<<\<target/\>>>> tag. Only <<<depends>>> attribute in Ant <<<\<target/\>>>> is not wrapped.
+ You can specify Ant {{{http://ant.apache.org/manual/using.html#targets}<<<\<target/\>>>>}} attributes in the
+ <<<\<target/\>>>> tag. The plugin wraps all Ant <<<\<target/\>>>> attributes except <<<depends>>>.
+---+
[...]
@@ -99,19 +98,17 @@ Usage
* Additional source directories
- If your Ant tasks generate additional source code that needs to be added
- to the build, you can use the
- {{{http://www.mojohaus.org/build-helper-maven-plugin/}build-helper-maven-plugin}}.
- The <<<sourceRoot>>> and <<<testSourceRoot>>> options of the antrun plugin are removed as of version 3.0.0.
+ If your Ant tasks generate source code, use the
+ {{{http://www.mojohaus.org/build-helper-maven-plugin/}build-helper-maven-plugin}} to add the code to the
+ build. The <<<sourceRoot>>> and <<<testSourceRoot>>> options are removed in version 3.0.0.
* Using Maven properties
- All of the properties available to Maven are also available in the target
- configuration. However, you may want to call an external Ant build script
- using the <ant> task. To avoid name conflicts, only a subset of the properties
- are passed to the external Ant build. These include all properties defined in
- the <properties> section of the POM. It also includes prefixed versions of
- some of the commonly used Maven properties.
+ All Maven properties are also available in the target configuration. When
+ you call an external Ant build script with the <ant> task, the plugin passes
+ only a subset of the properties. The subset prevents name conflicts. The
+ subset includes all properties in the <properties> section of the POM. The
+ subset also includes prefixed versions of common Maven properties.
------
maven.project.groupId
@@ -120,8 +117,8 @@ Usage
etc.
------
- If the Maven property you want to use is not available in an external file, you
- will have to redefine the property before calling <ant>.
+ If a Maven property is not available in an external file, define the
+ property before you call <ant>.
+---+
<property name="maven.project.url" value="\${project.url}"/>
@@ -130,9 +127,8 @@ Usage
* Ant Expressions to Maven Expressions Mapping
- Some Ant expressions have their respective counterparts in Maven. Thus, one
- can simply invoke the corresponding Maven expression instead of using
- maven-antrun-plugin to avoid the unneccessary overhead.
+ Some Ant expressions have a counterpart in Maven. You can use the Maven
+ expression instead of maven-antrun-plugin. This avoids extra work.
*-----------------------------------+-----------------------------------+
| <<Ant Expression>> | <<Maven Expression>> |
@@ -227,4 +223,3 @@ Usage
| <<<Translate>>> | {{{../maven-resources-plugin/}<<<maven-resources-plugin>>>}} |
| | <Note: Translate can specify its own tokens and can have a different encoding scheme for reading and writing files. maven-resources-plugin however uses the \${...} annotation only and has only one encoding scheme for reading and writing> |
*-----------------------------------+-----------------------------------+
-
diff --git a/src/site/fml/faq.fml b/src/site/fml/faq.fml
index 8205d57..7aff8aa 100644
--- a/src/site/fml/faq.fml
+++ b/src/site/fml/faq.fml
@@ -27,14 +27,13 @@ under the License.
<faq id="Why use antrun and not the Ant program itself?">
<question>Why use antrun and not the Ant program itself?</question>
<answer>
- <p>Maven has certain benefits over Ant. And for your Ant projects to take
- advantage of these, you can use Maven as your project management tool and
- use its maven-antrun-plugin to build your Ant projects. </p>
- <p>Furthermore, if you wish to migrate from Ant to Maven, you can use
- this plugin first, then gradually convert your Ant expressions into their
- corresponding Maven expressions.</p>
+ <p>Maven has benefits over Ant. You can use Maven as your project
+ management tool. Use its maven-antrun-plugin to build your Ant
+ projects.</p>
+ <p>If you want to migrate from Ant to Maven, use this plugin first.
+ Then convert your Ant expressions into their Maven counterparts one by
+ one.</p>
</answer>
</faq>
</part>
</faqs>
-
diff --git a/src/site/xdoc/download.xml.vm b/src/site/xdoc/download.xml.vm
index d05c2ec..7340c16 100644
--- a/src/site/xdoc/download.xml.vm
+++ b/src/site/xdoc/download.xml.vm
@@ -29,9 +29,9 @@ under the License.
<p><strong>${project.name} ${project.version}</strong> is distributed in source format.</p>
- <p>Use a source archive if you intend to build <strong>${project.name}</strong> yourself.</p>
+ <p>Use a source archive to build <strong>${project.name}</strong> yourself.</p>
- <p>Otherwise, simply use the ready-made binary artifacts from <strong>central repository</strong>.</p>
+ <p>Otherwise, use the ready-made binary artifacts from the <strong>central repository</strong>.</p>
<p><strong>${project.name}</strong> is distributed under the <a href="https://www.apache.org/licenses/">Apache License, version 2.0</a>.</p>
@@ -58,18 +58,17 @@ under the License.
</tbody>
</table>
- <p>It is essential that you <a href="https://www.apache.org/info/verification.html">verify the integrity</a> of the downloaded file
- using the checksum (.sha512 file)
- or using the signature (.asc file) against the public <a href="https://downloads.apache.org/maven/KEYS">KEYS</a> used by the Apache Maven developers.
+ <p>Verify the integrity of the downloaded file. Use the checksum
+ (.sha512 file) or the signature (.asc file). Verify the signature
+ against the public <a href="https://downloads.apache.org/maven/KEYS">KEYS</a> used by the Apache Maven developers.
</p>
</subsection>
<subsection name="Previous Versions">
- <p>It is strongly recommended to use the latest release version of <strong>${project.name}</strong> to take advantage of the newest features and bug fixes.</p>
- <p>Older non-recommended releases can be found on our <a href="https://archive.apache.org/dist/maven/plugins/">archive site</a>.</p>
+ <p>Use the latest release version of <strong>${project.name}</strong>. The latest version has the newest features and bug fixes.</p>
+ <p>You can find older releases on the <a href="https://archive.apache.org/dist/maven/plugins/">archive site</a>.</p>
</subsection>
</section>
</body>
</document>
-