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
GRECLIPSE
  • GRECLIPSE
  • GRECLIPSE-886 End-User configurable content assist ...
  • GRECLIPSE-899

Inferencing DSL event trace view

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Sub-task Sub-task
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.1.0Release
  • Fix Version/s: 2.1.1Release
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

Should create an event trace view to see the results of inferencing DSL compilation, to look at problems, etc. This could be based on the AJDT Event Trace view. Probably best to make this a console.

Also, probably best to put this into org.codehaus.groovy.eclipse.core/ui, rather than in the dsl plugins.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Andrew Eisenberg added a comment - 24/Nov/10 11:31 PM

I just committed the Groovy Event Console. You can open it like any other console in the console view. Events will be logged to it only when the console is open.

To log an event do this:

GroovyLogManager.manager.log(TraceCategory.COMPILER, "Message")

I created a few arbitrary categories. I can easily expand them on request. Each category is associated with a color in the console.

You can also check to see if there are any loggers registered. This way you don't have to waste time constructing a message if there's no where to log to:

GroovyLogManager.manager.hasLoggers()

The following enables the default logger that logs to sysout:

GroovyLogManager.manager.setUseDefaultLogger(true)

This functionality is in org.codehaus.groovy bundle, so it will be available from any other bundle in groovy-eclipse except the core patch.

Show
Andrew Eisenberg added a comment - 24/Nov/10 11:31 PM I just committed the Groovy Event Console. You can open it like any other console in the console view. Events will be logged to it only when the console is open. To log an event do this: GroovyLogManager.manager.log(TraceCategory.COMPILER, "Message" ) I created a few arbitrary categories. I can easily expand them on request. Each category is associated with a color in the console. You can also check to see if there are any loggers registered. This way you don't have to waste time constructing a message if there's no where to log to: GroovyLogManager.manager.hasLoggers() The following enables the default logger that logs to sysout: GroovyLogManager.manager.setUseDefaultLogger( true ) This functionality is in org.codehaus.groovy bundle, so it will be available from any other bundle in groovy-eclipse except the core patch.
Hide
Permalink
Andrew Eisenberg added a comment - 24/Nov/10 11:32 PM

Now available. I may add some new commands to the logger, like scroll lock, but it's really meant to be just a simple logger with no magical functionality.

Show
Andrew Eisenberg added a comment - 24/Nov/10 11:32 PM Now available. I may add some new commands to the logger, like scroll lock, but it's really meant to be just a simple logger with no magical functionality.

People

  • Assignee:
    Andrew Eisenberg
    Reporter:
    Andrew Eisenberg
Vote (0)
Watch (0)

Dates

  • Created:
    24/Nov/10 4:42 PM
    Updated:
    24/Nov/10 11:32 PM
    Resolved:
    24/Nov/10 11:32 PM
  • 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.