Java version automatically change to java 1.5 after maven update

前端 未结 11 495
盖世英雄少女心
盖世英雄少女心 2020-12-22 17:29

I am using eclipse as IDE. When I right click on the project and then click maven update my java version change to 1.5. Here is what I did so far, I followed all the steps l

相关标签:
11条回答
  • 2020-12-22 17:59

    Had the same issue when I installed Java 9. My project would default to J2SE-1.5 Execution Environment. Strangely, Java 9 compliance level is not referenced like previous versions, i.e. "1.8", but as "9". So I had to provide my properties and Maven compiler plugin config accordingly:

    <properties>
        <maven.compiler.source>9</maven.compiler.source>
        <maven.compiler.target>9</maven.compiler.target>
    </properties>
    

    and

    <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <configuration>
            <source>9</source>
            <target>9</target>
        </configuration>
    </plugin>
    

    This seems to have solved the problem. Works for versions 9 and above.

    0 讨论(0)
  • 2020-12-22 18:04

    I am using Java 11. This is how the complete pom.xml file looks like after adding <properties> and <plugin>

    <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
      <modelVersion>4.0.0</modelVersion>
      <groupId>com.akshay</groupId>
      <artifactId>1000SpringSecurityEg</artifactId>
      <packaging>war</packaging>
      <version>0.0.1-SNAPSHOT</version>
      <name>1000SpringSecurityEg Maven Webapp</name>
      <url>http://maven.apache.org</url>
        
      <dependencies>
        <dependency>
          <groupId>junit</groupId>
          <artifactId>junit</artifactId>
          <version>3.8.1</version>
          <scope>test</scope>
        </dependency>
      </dependencies>
      
        <properties>
            <javaVersion>11</javaVersion>
            <maven.compiler.source>${java.version}</maven.compiler.source>
            <maven.compiler.target>${java.version}</maven.compiler.target>
        </properties>
      
      <build>
        <finalName>1000SpringSecurityEg</finalName>
        
            <plugins>
                <plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-compiler-plugin</artifactId>
                    <version>3.8.1</version>
                    <configuration>
                        <source>11</source>
                        <target>11</target>
                    </configuration>
                </plugin>
            </plugins>
            
      </build>
    </project>
    

    The above code worked for me. Hope it works for you as well.

    0 讨论(0)
  • 2020-12-22 18:05

    I encounter similar issue on one of my team mate machine. He was using old version of Eclipse, I believe it he was using Keppler. Project after being updated change JRE version to 1.5.

    Simple updating Eclipse to latest version solve this problem.

    0 讨论(0)
  • 2020-12-22 18:06

    I've resolved the issue installing the eclipse update "JAVA 12" from the market. It makes my eclipse pass from Kepler to Luna.

    After that, i have been able to set 1.8 as standard JDK, fixing the "maven update" problem.

    0 讨论(0)
  • 2020-12-22 18:09

    In my case (old JBoss Developer Studio), the issue was the JRE environments did not include 1.8 (only 1.7). When I switched the maven-compiler-plugin version to 1.7 and did maven update project, it updated the Eclipse JRE system library to 1.7.

    So the solution is to either get a newer IDE version that includes a built-in JRE environment that is 1.8 or later, or try to install it manually (see https://stackoverflow.com/a/35204314)

    0 讨论(0)
  • 2020-12-22 18:10

    I had this problem. In my case the <properties> tag & nested tags Jorge Campos mentions above were in the wrong place. If I put them between the <hostversion> and <dependencies> tags in the pom.xml file, then this behaviour stopped.

    That can be picked up in Eclipse if validation of these files is switched on.

    0 讨论(0)
提交回复
热议问题