This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 153053 - CP is not being refreshed
Summary: CP is not being refreshed
Status: RESOLVED WONTFIX
Alias: None
Product: groovy
Classification: Unclassified
Component: Editor (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Martin Janicek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-12 16:33 UTC by Lukas Jungmann
Modified: 2012-11-22 16:15 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Jungmann 2008-11-12 16:33:55 UTC 
-create a new java app
-copy some groovy script/file to it and open the file in the editor

=> editor correctly shows compilation errors

-go to project props and enable groovy there or add groovy-all.jar to project libraries

=> editor still shows compilation errors

workaround is to re-open the file
Comment 1 Martin Janicek 2012-11-22 16:15:15 UTC 
Closing as WONTFIX. In the current version there is no other way how to activate groovy than by creating new Script/Class/Groovy JUnit test. And those actions refresh CP correctly. The old groovy project properties tab was deleted about a release ago because it wasn't much useful and it caused some other issues.

I know it isn't a nicest solution but from my point of view the only other option we got here is to add groovy as a part of standard java application (which I don't think we should do with current groovy support ;))