jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
Signup
groovy
  • groovy
  • GROOVY-4679

Add debug mode

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 1.7.8
  • Fix Version/s: None
  • Component/s: Grape
  • Labels:
    None
  • Number of attachments :
    0

Description

Add a debug mode for the resolver and the grab statement. If you have trouble, slow servers, bad proxys etc., it is completely intransparent what's happening.
Since this feature is meant for scripts some console output would be great.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Antony Stubbs added a comment - 30/Nov/12 6:13 PM

This is badly needed for ties when grab doesn't do what you expect. It doesn't even look like it's running for me.

Show
Antony Stubbs added a comment - 30/Nov/12 6:13 PM This is badly needed for ties when grab doesn't do what you expect. It doesn't even look like it's running for me.
Hide
Permalink
Guillaume Laforge added a comment - 03/Dec/12 4:16 AM

The Groovy Console does provide such feedback in the status bar.
But we've not added feedback for the groovy or groovysh commands.
People might be piping the output of a Groovy script to some other tool, and the Grab logging output might be interfering, so I'm not 100% sure it's a good idea. For groovysh this would be okay though I guess.

For reference, in the Groovy Console, we're installing an Ivy event logger here:
https://github.com/groovy/groovy-core/blob/master/subprojects/groovy-console/src/main/groovy/groovy/ui/Console.groovy#L226
And here:
https://github.com/groovy/groovy-core/blob/master/subprojects/groovy-console/src/main/groovy/groovy/ui/ConsoleIvyPlugin.groovy#L38

Show
Guillaume Laforge added a comment - 03/Dec/12 4:16 AM The Groovy Console does provide such feedback in the status bar. But we've not added feedback for the groovy or groovysh commands. People might be piping the output of a Groovy script to some other tool, and the Grab logging output might be interfering, so I'm not 100% sure it's a good idea. For groovysh this would be okay though I guess. For reference, in the Groovy Console, we're installing an Ivy event logger here: https://github.com/groovy/groovy-core/blob/master/subprojects/groovy-console/src/main/groovy/groovy/ui/Console.groovy#L226 And here: https://github.com/groovy/groovy-core/blob/master/subprojects/groovy-console/src/main/groovy/groovy/ui/ConsoleIvyPlugin.groovy#L38
Hide
Permalink
Antony Stubbs added a comment - 11/Dec/12 4:18 PM

If they're piping output, can they turn all debuggin off with an option?

What release is this new feedback scheduled for?

Show
Antony Stubbs added a comment - 11/Dec/12 4:18 PM If they're piping output, can they turn all debuggin off with an option? What release is this new feedback scheduled for?
Hide
Permalink
Pascal Schumacher added a comment - 19/Jan/13 2:54 AM - edited

I took a look at the source code (https://github.com/groovy/groovy-core/blob/master/src/main/groovy/grape/GrapeIvy.groovy#L369). There is already a debug mode. You just have to set the system property "groovy.grape.report.downloads" to "true" (e.g. add "-Dgroovy.grape.report.downloads=true" to JAVA_OPTS) and Grape will print the following infos to System.error:

  • Starting to resolve a dependency
  • Starting to download an artifact
  • Retrying to download an artifact (Grape tries eight times)
  • Download size and time for downloaded artifacts
Show
Pascal Schumacher added a comment - 19/Jan/13 2:54 AM - edited I took a look at the source code ( https://github.com/groovy/groovy-core/blob/master/src/main/groovy/grape/GrapeIvy.groovy#L369 ). There is already a debug mode. You just have to set the system property "groovy.grape.report.downloads" to "true" (e.g. add "-Dgroovy.grape.report.downloads=true" to JAVA_OPTS) and Grape will print the following infos to System.error: Starting to resolve a dependency Starting to download an artifact Retrying to download an artifact (Grape tries eight times) Download size and time for downloaded artifacts
Hide
Permalink
Guillaume Laforge added a comment - 21/Jan/13 4:16 AM

You can use the system properties mentioned by Pascal already.
I'm closing the issue as "won't fix" as there's not more work to be done here since it's been already covered in an earlier version.

Show
Guillaume Laforge added a comment - 21/Jan/13 4:16 AM You can use the system properties mentioned by Pascal already. I'm closing the issue as "won't fix" as there's not more work to be done here since it's been already covered in an earlier version.

People

  • Assignee:
    Guillaume Laforge
    Reporter:
    Haug Bürger
Vote (1)
Watch (3)

Dates

  • Created:
    16/Feb/11 2:32 AM
    Updated:
    21/Jan/13 2:13 PM
    Resolved:
    21/Jan/13 4:16 AM
  • Atlassian JIRA (v5.2.7#850-sha1:b2af0c8)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.