This is an automated email from the ASF dual-hosted git repository. elharo pushed a commit to branch maven2 in repository https://gitbox.apache.org/repos/asf/maven-compiler-plugin.git
commit ddafe951f53ae316a7a0f0eb02e124bc9c8551bc Author: Elliotte Rusty Harold <[email protected]> AuthorDate: Mon Jun 19 16:26:12 2023 -0400 Remove references to old Maven versions. In 2023 assume everyone is on 3.3.1 or later. --- src/site/apt/examples/module-info.apt.vm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/site/apt/examples/module-info.apt.vm b/src/site/apt/examples/module-info.apt.vm index 48669a4..6516717 100644 --- a/src/site/apt/examples/module-info.apt.vm +++ b/src/site/apt/examples/module-info.apt.vm @@ -54,8 +54,8 @@ Older projects with module-info In case you want the project to be Java 6, 7 or 8 compatible, you can simply use JDK 9 for both execution blocks. The easiest way is to use Java 9 as the runtime for Maven, by setting <<<JAVA_HOME=/path/to/jdk-9>>> before running <<<mvn>>>. - 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) - or a custom jdkToolchain (supported since Maven 3.3.1) and refer to the JDK 9 installation on your system. + But if you want to use an older Java runtime for Maven, you can use the maven-toolchain-plugin to specify the shared JDK + or a custom jdkToolchain and refer to the JDK 9 installation on your system. +------- <project>
