[
https://jira.codehaus.org/browse/MECLIPSE-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355079#comment-355079
]
Stefan Seifert commented on MECLIPSE-641:
-----------------------------------------
is there any chance of getting this into the next release?
the code change is really minimal (swaps the ordering of two statements).
it allows provisioning generated eclipse project files with preconfigured
project-specific eclipse settings, and makes sure that the the pom-derived
settings are applied as well.
it even works in combination with m2eclipse eclipse:eclipse is called before
importing the project as maven project into eclipse.
> org.eclipse.jdt.core.prefs doesn't get updated with source and target version
> -----------------------------------------------------------------------------
>
> Key: MECLIPSE-641
> URL: https://jira.codehaus.org/browse/MECLIPSE-641
> Project: Maven Eclipse Plugin
> Issue Type: Bug
> Components: M2Eclipse support
> Affects Versions: 2.8
> Environment: Linux ia32,
> maven-eclipse-plugin-2.8-20100216.071109-292, Maven 2.2.1
> Reporter: Johan Walles
> Attachments: 121016_MECLIPSE-641_additionalConfig.patch
>
>
> * 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.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
