compiling project with jdk1.5 using maven2

Question

i managed to create my project structure using maven2. but when am compiling my project using mvn install getting error generics are not supported in -source 1.3

googled to build my project using jdk1.5 and added build tag

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.myProject</groupId>
  <artifactId>project</artifactId>
  <packaging>jar</packaging>
  <version>1.0-SNAPSHOT</version>
  <name>myapp</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>
  <build>
   <plugins>
       <plugin>
           <groupId>com.myProject</groupId>
           <artifactId>project</artifactId>
           <configuration>
               <source>1.5</source>
               <target>1.5</target>
           </configuration>
       </plugin>
     <plugins>
  </build>
</project>

but this is not working.

Any hints?

ivo · Accepted Answer · 2009-05-25 16:49:34Z

4

Add the maven-compiler-plugin to your build:

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

answered May 25, 2009 at 16:49

ivo

4,2315 gold badges35 silver badges42 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Thilo Over a year ago

That's what I am doing, too. But is this really the easiest way? I thought Maven was all about "convention over configuration", but everyone must be using this (unintuitive) setting these days. Will they change the default one day (maybe with Maven 3)?

Sebastian · Accepted Answer · 2013-02-07 03:46:00Z

0

There's an "easier" way to accomplish this, without having to paste the same snippet all over your modules. You can set up a reactor and then you refer to it from all the other modules, like this:

  <parent>
    <groupId>com.foo.bar</groupId>
    <artifactId>reactor</artifactId>    
    <version>1.0-SNAPSHOT</version>
  </parent>

In the pom file of your reactor you have to put this:

<packaging>pom</packaging>

To let maven know that it's not a jar/war, etc.

Hope it helps

answered Feb 7, 2013 at 3:46

Sebastian

1181 gold badge2 silver badges11 bronze badges

Collectives™ on Stack Overflow

compiling project with jdk1.5 using maven2

2 Answers 2

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related