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)
  • GRECLIPSE
  • GRECLIPSE-286

Errors in Content Assist and Evaluation within Eclipse Scrapbook pages

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.0m1
  • Fix Version/s: 2.0.1Release
  • Component/s: Compiler Integration, Content Assist
  • Labels:
    None
  • Environment:
    Eclipse 3.4.2 (masquerading as MyEclipse 7.5) on Windows XP under JDK 1.6.13 (or maybe .14)

Description

With the alpha version of the plug-in for Eclipse 3.4.2 installed, I'm unable to use Content Assist or evaluate snippets of code within Scrapbook pages. I'm guessing that Eclipse is confused about whether the source is Groovy or Java, but I don't really know for sure. See the attached Eclipse error log export file (ScrapbookPageProblems.log) for details.

  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. Text File
    ScrapbookPageProblems.log
    04/Aug/09 2:22 PM
    21 kB
    Matt Passell

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Andrew Eisenberg added a comment - 10/Aug/09 1:58 PM

The errors that you see here are coming out because the CompilerOptions object is not properly set with the groovy options. My guess is that the CompilerOptions object should be augmented somewhere around o.e.j.internal.Evaluator.getCompiler().

Assigning this to Andy, since this appears to be his area.

Show
Andrew Eisenberg added a comment - 10/Aug/09 1:58 PM The errors that you see here are coming out because the CompilerOptions object is not properly set with the groovy options. My guess is that the CompilerOptions object should be augmented somewhere around o.e.j.internal.Evaluator.getCompiler(). Assigning this to Andy, since this appears to be his area.
Hide
Permalink
Andy Clement added a comment - 11/Aug/09 7:23 PM

The exception is now demoted to something less severe and the code will be treated as Java.

The decision to make here is how to decide that the code should be treated as groovy. From a UI point of view I don't know how to get to the project or if there is an associated project from inside the evaluator.

Show
Andy Clement added a comment - 11/Aug/09 7:23 PM The exception is now demoted to something less severe and the code will be treated as Java. The decision to make here is how to decide that the code should be treated as groovy. From a UI point of view I don't know how to get to the project or if there is an associated project from inside the evaluator.
Hide
Permalink
Andrew Eisenberg added a comment - 12/Aug/09 12:40 PM

I wonder if it makes sense to create a "groovy scrapbook page" editor and a "Groovy display view". These will both only handle groovy code.

Show
Andrew Eisenberg added a comment - 12/Aug/09 12:40 PM I wonder if it makes sense to create a "groovy scrapbook page" editor and a "Groovy display view". These will both only handle groovy code.
Hide
Permalink
Matt Passell added a comment - 12/Aug/09 1:28 PM

Andrew's suggestion would be fine with me. After all, scrapbook pages are so dynamic and loosely-defined, I can't exactly expect you to be able to auto-detect that an arbitrary snippet of code is Groovy or Java.

Show
Matt Passell added a comment - 12/Aug/09 1:28 PM Andrew's suggestion would be fine with me. After all, scrapbook pages are so dynamic and loosely-defined, I can't exactly expect you to be able to auto-detect that an arbitrary snippet of code is Groovy or Java.
Hide
Permalink
Andrew Eisenberg added a comment - 23/Dec/09 11:44 PM

The initial problem reported here is fixed. Closing this bug.

Post 2.0, we will look into better debug support, which will include looking at scrapbook pages for groovy.

Show
Andrew Eisenberg added a comment - 23/Dec/09 11:44 PM The initial problem reported here is fixed. Closing this bug. Post 2.0, we will look into better debug support, which will include looking at scrapbook pages for groovy.

People

  • Assignee:
    Andrew Eisenberg
    Reporter:
    Matt Passell
Vote (0)
Watch (1)

Dates

  • Created:
    04/Aug/09 2:22 PM
    Updated:
    04/Mar/11 11:12 AM
    Resolved:
    23/Dec/09 11:44 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.