Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Compiler version weirdness

I just tested this and with the staged 0.12.0 version of m2e core, the jre version is set correctly. I tested with a project defining maven-compiler-plugin v2.3.2 and configured with source/target to 1.6.
However, I know from experience that this was an issue with older versions (0.10.0 and most likely 0.10.2) of m2e-core.

As a workaround when this doesn't work automatically upon import or creating a Maven project, forcing a "Update Project Configuration" fixes it.


On Wed, Nov 3, 2010 at 22:07, Fred Bricon <fbricon@xxxxxxxxx> wrote:

starting from version 2.3.2, maven-compiler-plugin defaults to source 1.5. This is the version defined by default in maven 3.0 final, previous versions used source = 1.4.

In order for m2eclipse to configure java source compiler to 1.5 by default, you need to either lock the maven-compiler-plugin version in your pom (highly advised) :

or you can pick an m2eclipse-core plugin based on maven 3.0 (0.12.0 has been staged here [1]). However, due to an incompatibility between core 0.12.0 and current m2e-wtp 0.11.0, you'd better wait for a fix in the next few days before upgrading.



Fred Bricon

2010/11/3 David Balažic <david.balazic@xxxxxxxxxxxx>


I use Eclipse Java EE Helios SR-1
and m2eclipse items:
 - feature 0.10.2
 - subclipse.feature 0.10.0
 - scm.feature 0.10.0
 - wtp.feature

I created a new maven project and noticed that the Eclipse classpath and compiler versions
are set to 1.4.

This page* says:
the default source setting is 1.5 and the default target setting is 1.

So I wonder why does m2eclipse configure 1.4 in the Eclipse project.

* -

David Balažic
m2e-users mailing list

"Have you tried turning it off and on again" - The IT Crowd

m2e-users mailing list

Back to the top