[MECLIPSE-506] Property of parent project not resolved

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.5.1
• Environment: Maven version: 2.0.9; Java version: 1.6.0_07; OS name: "linux" version: "2.6.24-22-generic" arch: "i386" Family: "unix"
• Assignee: Unassigned
• Reporter: Benjamin Voigt
• Created: 05/Dec/08 08:19
• Updated: 25/Nov/14 14:48
• Resolved: 25/Nov/14 14:48

Description

We have a corporate pom in our company which set various properties, on of them is the source and target for the compiler plugin. It does this by defining a property "project.build.jdk" which is then referenced in the configuration section of the compiler plugin (under build/pluginManagement/plugins/). Our default value for this property is "1.5".

Now there's a single module project which inherits from this corporate pom. At compilation, the project.build.jdk ist properly resolved to 1.5, but when eclipse:eclipse is called, the following is put into the .settings/org.eclipse.jdt.core.prefs :
org.eclipse.jdt.core.compiler.codegen.targetPlatform=${project.build.jdk}
eclipse.preferences.version=1
org.eclipse.jdt.core.compiler.source=${project.build.jdk}
org.eclipse.jdt.core.compiler.compliance=${project.build.jdk}

It seems that this property (an maybe others) aren't resolved.

Issue Links

• duplicates: MECLIPSE-537 Failed to produce a correct "org.eclipse.jdt.core.prefs" file with eclipse:eclipse
• duplicates: MECLIPSE-460 Configure eclipse to use same source/target version as configured in maven-compiler-plugin.
• duplicates: MECLIPSE-463 IdeUtils determine unresolved values from maven-compiler-plugin
• relates to: MECLIPSE-543 custom properties not being evaluated before being referenced