> What JREs you have installed in Eclipse?
Sun SDK 1.5, Sun SDK 1.6, IBM SDK 1.5, IBM SDK 1.6, Harmony SDK 1.5
Execution Environments defined for J2SE 1.2 up to J2SE 1.6
> The current logic in project updater is that it tries to detect currently
> installed JREs and sets project settings based on the best match between
> installed JREs and settings from maven-compiler-plugin. JRE set as default
> in Eclipse or JRE used to run Eclipse is not being used (unless there is no
> maven-compiler-plugin configuration available from the project pom, then it
> is defaulted to the workbench JRE).
Yes, you check if the current JRE is compatible with POM requirement
but the .project could be used by another developper with a different
'default JRE'.
> However, you probably seeing the effects of plugin configuration not being
> inherited from the parent projects or from pluginManagement, eg.
> MNGECLIPSE-545
May be
> BTW, we probably don't need to detect the installed JREs and should always
> select container based on the Maven settings, then let JDT to do the
> matching. Igor, what do you think about this one?
Or may if the current classpath is like
org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5,
stay it like this ?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
