m2e configures JDT to use the same compiler level as used by maven from
command line, which is 1.4 by default.
There is no option to use workspace default compiler level as this would
make builds too environment dependent, but you can tell
maven-compiler-plugin to use non-default compiler level in pom.xml and m2e
will honour this configuration (you'll need to right-click->Maven->Update
Project Configuration for this to take effect)
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.5</source>
<target>1.5</target>
</configuration>
</plugin>
</plugins>
</build>
--
Regards,
Igor
> More specifically, org.eclipse.jkt.core.prefs
>
> Why does the plugin do this? I was playing around with creating a new
> sample project from an archetype. When I looked at the project
> settings, I noticed that my JDK compliance was set to 1.4. Is their an
> option to not create these eclipse settings so that my project could use
> my workspace settings? Or at least can I specify the values to use when
> the plugin creates these eclipse .setting files?
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
