Henri,
What JREs you have installed in Eclipse?
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).
However, you probably seeing the effects of plugin configuration not
being inherited from the parent projects or from pluginManagement, eg.
MNGECLIPSE-545
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?
regards,
Eugene
Henri Gomez wrote:
version 0.9.4
Right click on Projet
Maven / Update Project Configurations
What I see in maven 2 console ...
7/9/08 3:20:14 PM CEST: Adding source folder /mycorp-app/src/main/java
7/9/08 3:20:14 PM CEST: Adding source folder /mycorp-app/src/test/java
7/9/08 3:20:14 PM CEST: Adding resource folder /mycorp-app/src/main/resources
7/9/08 3:20:14 PM CEST: Adding resource folder /mycorp-app/src/test/resources
7/9/08 3:20:14 PM CEST: Setting source compatibility: 1.5
7/9/08 3:20:14 PM CEST: Setting target compatibility: 1.5
7/9/08 3:20:14 PM CEST: JRE compliant to 1.5.
org.eclipse.jdt.launching.JRE_CONTAINER[CPE_CONTAINER][K_SOURCE][isExported:false]
7/9/08 3:20:14 PM CEST: Updated source folders for project
slib-go-xylos-opcvm 0sec
Maven see we need 1.5 for both source and target. It also detect the
default JRE use by Eclipse is 1.5 compliant, so set the JRE to
CONTAINER.
Problem, if other developpers are using Java 1.4 ou 1.6 as default
JRE, we could be in trouble.
Thanks
2008/7/9 Eugene Kuleshov <[EMAIL PROTECTED]>:
Henri,
Can you please post screenshot from the Window / Preferences... / Java /
Installed JREs? Also, what version of m2eclipse you are using?
regards,
Eugene
Henri Gomez wrote:
All our poms define Java 1.5 support for both source and target.
In our .classpath we use to have :
<classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5"/>
After doing an 'update project configuration' the .classpath turn to :
<classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
Could you keep the current classpath config for JRE if it match pom level
?
Thanks
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
