Henri Gomez wrote:
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'.
I understand and that is why
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 ?
Unfortunately that is not going to work, because if pom.xml has
changed we do need to update JRE container accordingly. I am always done
implementing MNGECLIPSE-646, which should address this. Later we are
planning to give some warnings when JDT settings don't match pom.xml,
that should include JRE container and compiler settings, source folders
and anything else project configurators care about.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
