Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove duplicate content #28

Merged
merged 1 commit into from
Apr 11, 2024
Merged

Remove duplicate content #28

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 7 additions & 14 deletions src/site/apt/index.apt.vm
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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}}.