You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2015/05/27 13:58:17 UTC
[jira] [Commented] (MNG-5832) Cannot override systemPath with
dependencyManagement
[ https://issues.apache.org/jira/browse/MNG-5832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560840#comment-14560840 ]
Michael Osipov commented on MNG-5832:
-------------------------------------
Though this does not help: System scope is deprecated and the {{tools.jar}} is about to disappear because the internal image of the JRE installation won't be transparent anymore.
> 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
>
> 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)