Skip to content

Commit ae3a423

Browse files
authored
Remove references to old Maven versions. (#194)
* Remove references to old Maven versions. In 2023 assume everyone is on 3.3.1 or later.
1 parent 92c51bb commit ae3a423

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

src/site/apt/examples/module-info.apt.vm

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -54,8 +54,8 @@ Older projects with module-info
5454
In case you want the project to be Java 6, 7 or 8 compatible, you can simply use JDK 9 for both execution blocks.
5555

5656
The easiest way is to use Java 9 as the runtime for Maven, by setting <<<JAVA_HOME=/path/to/jdk-9>>> before running <<<mvn>>>.
57-
But if you want to use an older Java runtime for Maven, you can use the maven-toolchain-plugin to specify the shared JDK (supported since Maven 2.0.9)
58-
or a custom jdkToolchain (supported since Maven 3.3.1) and refer to the JDK 9 installation on your system.
57+
But if you want to use an older Java runtime for Maven, you can use the maven-toolchain-plugin to specify the shared JDK
58+
or a custom jdkToolchain and refer to the JDK 9 installation on your system.
5959

6060
+-------
6161
<project>
@@ -106,10 +106,9 @@ Older projects with module-info
106106

107107
* Java 5 or below Compatibility
108108

109-
Given Maven 3 requires newer Java release at runtime, you'll absolutely need to use Toolchains to use a JDK different from
109+
Given that Maven 3 requires newer Java release at runtime, you'll absolutely need to use Toolchains to use a JDK different from
110110
Maven runtime.
111111

112-
Be aware that you will need at least Maven 3.3.1 to specify a custom jdkToolchain in your plugin configuration.
113112
You could add a jdkToolchain to do base-compile execution-block as well referring to JDK 5.
114113

115114
+-------

0 commit comments

Comments
 (0)