You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@groovy.apache.org by "Eric Milles (Jira)" <ji...@apache.org> on 2024/08/24 13:18:00 UTC

[jira] [Commented] (GROOVY-11454) Expand on debugging GrapeIvy.groovy

    [ https://issues.apache.org/jira/browse/GROOVY-11454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876427#comment-17876427 ] 

Eric Milles commented on GROOVY-11454:
--------------------------------------

Did you try setting system property "ivy.message.logger.level" to 0, 1, 2, 3 or 4?  This should enable Ivy logging to sysout.

Settings are loaded from file given by "grape.confg" system property or "~/.groovy/grapeConfig.xml" or "defaultGrapeConfig.xml" from groovy jar.

> 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)