Re: [m2e-users] Compiler version weirdness

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

It's hard to say much without looking at the project, but I am guessing
something in the project configuration confuses m2e and it can read
maven-compiler-plugin configuration properly. Try setting up custom
lifecycle mapping as explain in [1]. Open a bug in m2e jira [2] with
sample project and steps to reproduce the problem if custom lifecycle
mapping does not work.


[1] https://docs.sonatype.org/pages/viewpage.action?pageId=2949459
[2] https://issues.sonatype.org/browse/MNGECLIPSE

--
Regards,
Igor

On 10-11-03 12:27 PM, David Balažic wrote:
> Hi!
>
> 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 0.11.0.20101024-0955
>
> 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.
>
> * - http://maven.apache.org/plugins/maven-compiler-plugin/
>
>
> David Balažic