Specifying Java Version in Maven: Properties vs. Compiler Plugin - What's the Difference?

Specifying Java Version in Maven: Differences Between Properties and Compiler Plugin

Question: How do the approaches of setting the Java version through properties and the Maven compiler plugin differ?

Answer: There are three common ways to specify the Java version in Maven:

• Spring Boot Feature: Exclusive to Spring Boot projects, it allows setting both source and target versions with the same value using the property.
• Maven Compiler Plugin with Source and Target: Using and properties or configuring them in the compiler plugin is equivalent. Both methods set the Java source and target versions.
• Maven Compiler Plugin with Release: Introduced in version 3.6, this method uses the maven.compiler.release property to set the source, target, and bootstrap JVM options based on a specified Java release version (e.g., "9" for Java 9).

Best Practices:

Java 8 and below: Using and properties or configuring them in the compiler plugin is preferred.

Java 9 and above: The maven.compiler.release property is a concise and recommended approach to set the Java version and strongly couple the source, target, and bootstrap JVM options.

Cross-Compilation Compatibility:

If the JDK version used in JAVA_HOME differs from the version specified in the pom, ensure that the compiler plugin specifies both the executable path of the target JDK version and the fork option set to true.

Maven Core Plugins:

Even if not explicitly declared in the pom, Maven uses core plugins, including the compiler plugin, for specific tasks like compiling code and executing tests. The goal can display the list of attached plugins and their configurations.

The above is the detailed content of Specifying Java Version in Maven: Properties vs. Compiler Plugin - What's the Difference?. For more information, please follow other related articles on the PHP Chinese website!