[
https://issues.apache.org/jira/browse/MNG-5832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schulte resolved MNG-5832.
------------------------------------
Resolution: Not A Problem
I am closing this. You can change that system path by moving a corresponding
dependency nearer to where it is used so that the 'nearest winst' strategy will
use that instead of something else. See method
[manageArtifact|http://maven.apache.org/ref/3.3.9/apidocs/src-html/org/apache/maven/repository/legacy/resolver/DefaultLegacyArtifactCollector.html#line.602].
> Cannot override systemPath with dependencyManagement
> ----------------------------------------------------
>
> Key: MNG-5832
> URL: https://issues.apache.org/jira/browse/MNG-5832
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.2.5
> Reporter: Marcin Wisnicki
> Assignee: Christian Schulte
>
> CRaSH has [invalid path|https://jira.exoplatform.org/browse/CRASH-225] to
> tools.jar in systemPath which causes errors during generation of maven site.
> I though I should be able to override it with dependencyManagement like so
> {code}
> <dependency>
> <groupId>com.sun</groupId>
> <artifactId>tools</artifactId>
> <version>1.7</version>
> <scope>system</scope>
> <systemPath>${java.home}/../lib/tools.jar</systemPath>
> </dependency>
> {code}
> but it seems to be ignored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
