Resolving Invalid Target Release Issues When Compiling Java 7 Code with Maven

Problem Phenomenon Analysis

When compiling Java 7 code with Maven, developers often encounter the "javac: invalid target release: 1.7" error message. From the provided case, although Java 7 is correctly installed in the system and environment variables appear properly configured, Maven still uses Java 6 during compilation execution.

The output from mvn clean install --debug clearly shows:

Apache Maven 3.0.3 (r1075438; 2011-02-28 11:31:09-0600)
Maven home: /usr/share/maven
Java version: 1.6.0_35, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home

This indicates that Maven's runtime environment is actually using Java 6, not the expected Java 7.

Root Cause Investigation

The core issue lies in the inconsistency between the Java version used when Maven starts and the environment variable configuration. Although the user correctly set JAVA_HOME and PATH in .zshrc, the Maven script may have hard-coded specific Java paths during startup.

The Maven startup script is typically located at /usr/share/maven/bin/mvn or similar paths. This script determines the Java version to use when starting, and if the script directly specifies a Java path, it will override the environment variable settings.

Solution Implementation

First, check the Java configuration in the Maven startup script:

# View mvn script content
cat /usr/share/maven/bin/mvn

# Or use which command to locate mvn script position
which mvn

Look for configuration lines similar to the following in the script:

JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home

If hard-coded Java paths are found, they can be modified to:

JAVA_HOME=${JAVA_HOME:-$(/usr/libexec/java_home)}

Or directly set to the correct Java 7 path:

JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_10.jdk/Contents/Home

Environment Variable Validation

Ensure environment variables take effect correctly:

# Verify JAVA_HOME
echo $JAVA_HOME

# Verify java command path
which java

# Verify Java version
java -version

# Verify javac version
javac -version

All commands should point to Java 7 version. If environment variables are correctly set but Maven still uses the wrong version, terminal restart or checking other configuration files may be necessary.

Maven Configuration Optimization

In addition to environment configuration, Maven's pom.xml configuration also needs proper setup:

<plugin>
    <artifactId>maven-compiler-plugin</artifactId>
    <version>3.0</version>
    <configuration>
        <source>1.7</source>
        <target>1.7</target>
    </configuration>
</plugin>

It's also recommended to update to newer Maven compiler plugin versions for better compatibility and feature support.

Preventive Measures

To prevent similar issues from recurring, it's advised to:

• Use /usr/libexec/java_home command to dynamically obtain Java paths
• Use version management tools like jEnv in multiple Java version environments
• Regularly check Maven and Java environment configurations
• Standardize development environment configurations in team development environments

Through systematic environment configuration checks and optimizations, version conflicts when compiling Java 7 code with Maven can be effectively resolved, ensuring development environment stability and consistency.