[MNG-2653] using ${version} for subproject dependencies doesn't work (maven uses 2.4.1 version instead)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Component/s: Inheritance and Interpolation
• Environment: win xp, maven 2.0.1, eclipse plugin 0.0.3, eclipse 3.1
• Assignee: kenneyw
• Reporter: Michal Stochmialek
• Created: 29/Dec/05 04:09
• Updated: 05/Apr/15 23:47
• Resolved: 16/Jun/07 03:57

Description

My project is a ear multiproject. It has 5 modules, that have internal dependencies. For example web module needs app and type modules.

I usually use following declaration for this kind of dependencies. Note that I'm using ${version} in dependency. In result I'm requesting foo-type jar of the same version as current project.

<project>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>foo</groupId>
<artifactId>foo</artifactId>
<version>0.0.1-SNAPSHOT</version>
</parent>
<artifactId>foo-app</artifactId>

<dependencies>
<dependency>
<groupId>foo</groupId>
<artifactId>foo-type</artifactId>
<version>${version}</version>
</dependency>
</dependencies>
</project>

This works from commandline, but doesn't work in eclipse plugin. I get following message:

"Unable to download the artifact from any repository foo:foo-type-2.4.1.jar"

Maven (or maven plugin) tries to download foo-type module in very strange version (instead 0.0.1-SNAPSHOT)!

I've attached simple multimodule project.

Issue Links

• depends upon: MNG-2651 POM interpolator treats ${pom.something} like ${something} and prefers system properties
• duplicates: MNG-2339 ${project.*} are interpreted in the wrong place
• is duplicated by: MECLIPSE-259 transitiv dependency version set to incorrect version 2.4.1
• is related to: MNG-2796 Yet another snapshot/timestamp version resolution problem