[MNG-4590] [regression] System properties are no longer interpolated in imported POMs

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0-alpha-7
• Fix Version/s: 3.0-beta-1
• Component/s: Dependencies
• Assignee: Benjamin Bentmann
• Reporter: Joerg Schaible
• Created: 15/Mar/10 03:18
• Updated: 30/Mar/10 14:46
• Resolved: 15/Mar/10 14:34

Description

We refer one artifact delivered with the JDK using a system scope:

<dependency>
  <groupId>com.sun</groupId>
  <artifactId>plugin</artifactId>
  <version>1.5.0</version>
  <scope>system</scope>
  <systemPath>${java.home}/lib/plugin.jar</systemPath>
</dependency>

This results with Maven 3.0-alpha7 (and 6) to the following error:

$ mi -Dpoms
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   The project projects:myproject-master:SNAPSHOT (/home/jos/work/projects/myproject/master/pom.xml) has 1 error
[ERROR]     For managed dependency com.sun:plugin:jar: system-scoped dependency must specify an absolute systemPath but is ${java.home}/lib/plugin.jar @ projects:general:4.1.2
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException

I did not report it for alpha6, because it is already fixed with MNG-4379, but apparently it is not. The dependency declaration works fine with 2.2.1, 2.1.0 and 2.0.10.