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 168054 - unable to resolbe class error messages
Summary: unable to resolbe class error messages
Status: RESOLVED DUPLICATE of bug 161176
Alias: None
Product: groovy
Classification: Unclassified
Component: Grails (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-02 16:36 UTC by dynoweb
Modified: 2009-07-07 14:58 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dynoweb 2009-07-02 16:36:08 UTC
In my grails project, I'm getting "unable to resolve class Xxxxx" error messages.  

I'm seeing this for two situations:

1. the missing class is a Java class in the src/java folder and the error is showing up in the groovy class which 
references the Java class.  The groovy source file doesn't show any errors, the compile status indicator on the top 
right is green, but the Tasks list shows the error messages.  It could be a refresh problem in the Tasks list.

2. the missing class for the second case is when it's not able to resolve a command object that was declared inside 
controller (A) and used in a different controller (B).  I think the parser doesn't think that command object's scope 
should allow controller (B) to see the command object. When this application runs, controller (B) is able to use that 
referenced command object.  (this groovy behavior seems strange coming from the java world if that was an inner class)
Comment 1 Petr Hejl 2009-07-07 14:58:07 UTC

*** This issue has been marked as a duplicate of 161176 ***