[
http://jira.codehaus.org/browse/MNG-4590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-4590:
-----------------------------------
Summary: [regression] System properties are no longer interpolated in
imported POMs (was: [regression] System properties are no longer interpolated
in system scope dependencies)
> [regression] System properties are no longer interpolated in imported POMs
> --------------------------------------------------------------------------
>
> Key: MNG-4590
> URL: http://jira.codehaus.org/browse/MNG-4590
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.0-alpha-7
> Reporter: Joerg Schaible
> Assignee: Benjamin Bentmann
> Attachments: MNG-4590.tar.gz, MNG-4590.zip
>
>
> We refer one artifact delivered with the JDK using a system scope:
> {code:xml}
> <dependency>
> <groupId>com.sun</groupId>
> <artifactId>plugin</artifactId>
> <version>1.5.0</version>
> <scope>system</scope>
> <systemPath>${java.home}/lib/plugin.jar</systemPath>
> </dependency>
> {code}
> This results with Maven 3.0-alpha7 (and 6) to the following error:
> {noformat}
> $ 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
> {noformat}
> 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.
--
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
