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 2024/04/11 11:43:15 UTC
(maven-toolchains-plugin) branch master updated: Remove duplicate content (#28)
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-toolchains-plugin.git
The following commit(s) were added to refs/heads/master by this push:
new 9b4ae95 Remove duplicate content (#28)
9b4ae95 is described below
commit 9b4ae9537017a8336fc32db359c2e5292cd48b31
Author: Elliotte Rusty Harold <el...@users.noreply.github.com>
AuthorDate: Thu Apr 11 11:43:09 2024 +0000
Remove duplicate content (#28)
and cleanup language
---
src/site/apt/index.apt.vm | 21 +++++++--------------
1 file changed, 7 insertions(+), 14 deletions(-)
diff --git a/src/site/apt/index.apt.vm b/src/site/apt/index.apt.vm
index 56250dc..6a65a88 100644
--- a/src/site/apt/index.apt.vm
+++ b/src/site/apt/index.apt.vm
@@ -25,22 +25,15 @@
${project.name}
- The Toolchains Plugins enables sharing configuration about tools across plugins,
- for example to make sure the plugins like compiler, surefire, javadoc, webstart etc. all use the same JDK for execution independently from JRE used to run Maven itself.
-
- Similarly to the maven-enforcer-plugin, it allows you to control environmental constraints in the build.
-
-* Discovery mechanism
-
- Since version 3.2.0, a new toolchains mechanism is provided. This relies on an automatic discovery mechanism based
- on an internal heuristic which tries to detect JDK from known locations. This mechanism is to be used with the
- <<<select-jdk-toolchain>>> goal, read about the {{{./toolchains/discovery.html}discovery mechanism}} for more
- informations.
+ The Toolchains Plugins enables sharing tool configuration across plugins;
+ for example, to make sure that plugins like compiler, surefire, and javadoc all use the same JDK for
+ execution, independently from JRE used to run Maven itself.
* Goals Overview
Since version 3.2.0, a new toolchains mechanism is provided. This relies on an automatic discovery mechanism based
- on an internal heuristic which tries to detect JDK from known locations. This mechanism is to be used with the goal:
+ on an internal heuristic which tries to detect JDK from known locations. Read about the {{{./toolchains/discovery.html}discovery mechanism}} for more
+ information. This mechanism is to be used with the goal:
* {{{./toolchain-mojo.html}toolchains:select-jdk-toolchain}} discover and selects a matching toolchain.
@@ -63,10 +56,10 @@ ${project.name}
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 feel like the plugin is missing a feature or has a defect, you can file a feature request or bug report in our
+ If the plugin is missing a feature or has a defect, you can file 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.
+ 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
{{{https://maven.apache.org/guides/development/guide-helping.html}guide to helping with Maven}}.