[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [m2e-users] Compiler version weirdness
- From: David Balažic <david.balazic@xxxxxxxxxxxx>
- Date: Thu, 4 Nov 2010 15:14:07 +0100
- Delivered-to: firstname.lastname@example.org
- Thread-index: AQHLfCio2jrQaKJUOUi7MjDqguiNaJNhXHXg
- Thread-topic: [m2e-users] Compiler version weirdness
"Update Project Configuration" did not do anything for me, the project still uses
Definig the compiler plugin 2.3.2 in pom on the other
hand did change the Java version to 1.5.
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
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>
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.
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
or you can pick
an m2eclipse-core plugin based on maven 3.0 (0.12.0 has been staged here
). 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
"Have you tried turning it off
and on again" - The IT