Eugene, I'm using m2eclipse version 0.9.6.20080905-0917. I'm pretty sure, after I changed pom and invoked update project configuration the eclipse classpath contained a concrete JRE reference. I've just reverted these changes and tried again. Now it did work correctly, strange...
I'll let you know when I can reproduce this issue again. Thanks, Holger Eugene Kuleshov wrote: > > > What version of m2eclipse you are using? See information about the > last releases at > http://docs.codehaus.org/display/M2ECLIPSE/New+and+Noteworthy > > It used to be that m2eclipse used concrete version of JRE, but it been > changed to use execution environments quite some time ago, though some > users don't like that either. > On a side note, there could be an issue with inheritance of the Maven > plugin settings, so project configurator don't see your settings. To say > for sure I would need to see the pom. > > regards, > Eugene > > > Holger Brands wrote: >> In some of our maven poms we have configured the java compiler source and >> target to 1.6. >> >> As far as I understand, calling update project configuration will adjust >> the >> Eclipse compiler and classpath settings accordingly, right? >> >> What we would like to use as eclipse classpath setting is the >> "JavaSE-1.6" >> execution environment, instead of a concrete JDK/JRE 1.6 >> version/installation. >> Is this possible with the current m2eclipse plugin? >> >> Thanks, >> Holger >> >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > -- View this message in context: http://www.nabble.com/update-project-configuration-and-compiler-classpath-settings-tp20288951p20291660.html Sent from the Maven Eclipse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
