You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Johan Walles (JIRA)" <ji...@codehaus.org> on 2010/02/17 17:30:55 UTC
[jira] Created: (MECLIPSE-641) org.eclipse.jdt.core.prefs doesn't
get updated with source and target version
org.eclipse.jdt.core.prefs doesn't get updated with source and target version
-----------------------------------------------------------------------------
Key: MECLIPSE-641
URL: http://jira.codehaus.org/browse/MECLIPSE-641
Project: Maven 2.x 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
* 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MECLIPSE-641) org.eclipse.jdt.core.prefs doesn't get
updated with source and target version
Posted by "Stefan Seifert (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MECLIPSE-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert updated MECLIPSE-641:
------------------------------------
Attachment: 121016_MECLIPSE-641_additionalConfig.patch
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.
> 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 2.x 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira