[
https://issues.apache.org/jira/browse/GROOVY-11454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876431#comment-17876431
]
Eric Milles commented on GROOVY-11454:
--------------------------------------
Instead of “ivy.settings.file” use “grape.config”
> Expand on debugging GrapeIvy.groovy
> -----------------------------------
>
> Key: GROOVY-11454
> URL: https://issues.apache.org/jira/browse/GROOVY-11454
> Project: Groovy
> Issue Type: Bug
> Components: Grape
> Reporter: Paul Hammant
> Priority: Major
>
> [https://github.com/apache/groovy/blob/f46103d31b7574ce883ff3b6c01fa8a412f225be/src/main/groovy/groovy/grape/GrapeIvy.groovy#L482]
> As well as getMessage() can more of the cause be communicated? I'm debugging
> why grapes is not working in a large corporate setting that has a working
> maven (and a corporate nexus). ~/.ivy2/ivysettings.xml is the one that says
> to use Maven settings.
> What I'm getting is that a grape was not found. I'm having to guess as to
> why, and coming up stumps. Ideally, I'd be told in which directory the jar
> was being looked for, and have my eureka from that.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
