[MNG-2446] parent Pom properties not resolved for module dependencies

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 2.0.4
• Component/s: Dependencies
• Environment: WindowsXP/Linux - JDK 1.4 last version
• Assignee: Brett Porter
• Reporter: Jeremie Poutrin
• Created: 14/Jul/06 10:08
• Updated: 17/Feb/10 09:18
• Resolved: 18/Dec/08 05:40

Description

root-project --> root-pom.xml with <version>${my.version}</version>

------->proj1 <parent><version>${my.version}</version></parent>
------->proj2 <parent><version>${my.version}</version></parent>
	->proj1 dependency
------->proj3 <parent><version>${my.version}</version></parent>

if I compile from the root-project directory, all compile fine.

if I compile from the proj2 directory, maven2 resolve proj2-${my.version}
resolve proj1-${my.version}
but tries to resolve the parent version root-project-${my.version} but this is not resolved.

Issue Links

• is related to: MNG-3057 properties not expanded in generated POMs when building A/B/C nested projects
• relates to: MNG-2412 global variable filtering of pom.xml for parent and sub module pom.xml files is not working when deploying to a repository.
• relates to: MNG-4369 Maven does not expand expressions while installing artifacts locally
• relates to: MNG-624 automatic parent versioning