generic not supported in 1.3 error even when java_home point jdk1.7 in maven build

Question

im getting below message when run mvn clean install

[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

D:\data\work\extjs.parser\src\main\java\com\model\Component.java:[17,15] error:
generics are not supported in -source 1.3

could not parse error message:   (use -source 5 or higher to enable generics)
D:\data\work\extjs.parser\src\main\java\com\model\Container.java:14: error: gene
rics are not supported in -source 1.3
    private List<Component> items;

the project is simple maven project but wont compile with generics error when i have already set JAVA_HOME to jdk1.7 installation path

however when i add plug in then it works fine. why is it required to explicitly set hava home path.

<plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-compiler-plugin</artifactId>
            <configuration>
                <source>1.7</source>
                <target>1.7</target>
                <showDeprecation>true</showDeprecation>
                <showWarnings>true</showWarnings>
                <executable>${env.JAVA_HOME}/bin/javac</executable>
                <fork>true</fork>
            </configuration>
        </plugin>

Ideally should not be the case, do one thing, try to run maven in debug mode. e.g. ** mvn -X clean install > test.log ** and analyze the log file to see the difference. — Himanshu Bhardwaj, Apr 05 '13 at 11:48
Thanks all for responding to my query. running maven with -X -e options helped. Also found that maven by default is using source as 1.5 hence it has to set explicitly. details on,http://stackoverflow.com/questions/21243619/why-maven-project-is-tied-to-j2se-1-5-by-default — Saurabh, Aug 03 '15 at 15:25

score 2 · Answer 1 · answered Mar 13 '14 at 10:18

You need to tell Maven to use JDK 1.5 to compile your source code explicitly. Declare Maven compiler plugin (maven-compiler-plugin) in your pom.xml file, like this :

<project ...>
  <dependencies>
   ...
  </dependencies>
  <build>
    <plugins>
       <plugin>
           <groupId>org.apache.maven.plugins</groupId>
           <artifactId>maven-compiler-plugin</artifactId>
           <version>2.3.1</version>
           <configuration>
               <source>1.5</source>
               <target>1.5</target>
           </configuration>
       </plugin>
    </plugins>
  </build>
</project>

score 1 · Answer 2 · answered Apr 05 '13 at 11:48

1

generics are not supported in -source 1.3

The error message is perfectly clear. You've told the compiler to compile in -source 1.3 mode, where there are no generics. So, there are no generics.

answered Apr 05 '13 at 11:48

user207421

305,947
44
307
483

1

Have a look at the question, in compiler plugin it is mentioned to use source and target as 1.7 – Himanshu Bhardwaj Apr 05 '13 at 12:24
1

The error message says otherwise, so it looks like his config is wrong. – Mark Rotteveel Apr 05 '13 at 12:31
@HimanshuBhardwaj I suggest you have a look at the error message. – user207421 Apr 05 '13 at 13:23
1

Thats why need to understand why the property isn't reflecting. – Himanshu Bhardwaj Apr 05 '13 at 14:18
@HimanshuBhardwaj I now suggest you have a look at the question. When he specifies the plugin you mention it works. The question is why it doesn't work *without* it, or indeed whether it is supposed to work at all. – user207421 Apr 05 '13 at 17:55

score 0 · Accepted Answer · answered Apr 28 '17 at 22:47

its old question. and after waiting for quite some time back then i didnt get answer. however while browsing maven compiler plugin docs i came to know that plugin has default settings. so earlier versions used to use jdk 1.3 as default for source/target and now it uses 1.5 e,g. after reading docs n running "mvn clean install -X" observed that,

Maven compile goal uses maven-compiler-plugin internally anyway
In pom, by specifying maven-compiler-plugin in build section, we can override certain configurations like source/target
if we don't specify then maven will use defaults given by "maven-compiler-plugin" itself which depends on its version.

Hence there was error till "maven-compiler-plugin" and its configurations(source/target) were not specified in pom.

generic not supported in 1.3 error even when java_home point jdk1.7 in maven build

3 Answers3