Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.8
-
Fix Version/s: None
-
Component/s: M2Eclipse support
-
Labels:None
-
Environment:Linux ia32, maven-eclipse-plugin-2.8-20100216.071109-292, Maven 2.2.1
-
Number of attachments :
Description
- Create a pom.xml that uses the <additionalConfig> tag to add a .settings/org.eclipse.jdt.core.prefs file to your project.
- In the same pom.xml, set Java source and target versions to 1.4 and 1.6.
- Do "mvn eclipse:eclipse"
Now, notice how the source and target settings in .settings/org.eclipse.jdt.core.prefs has whatever was in the <additionalConfig> file.
The source and target versions from your pom.xml are ignored.
I would like to have correct values for source and target filled in for Eclipse, even if I add a settings file manually.
attached is a patch with a solution for this problem:
121016_MECLIPSE-641_additionalConfig.patch
it changes the order in which the built-in generation of org.eclipse.jdt.core.prefs and the generation of additional config files takes place. if the latter is executed first the java version and encoding settings generated by eclipse plugin are merged with the own settings.