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 166831 - No code completion for Groovy classes in packages
Summary: No code completion for Groovy classes in packages
Status: RESOLVED FIXED
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-06-10 08:01 UTC by akochnev
Modified: 2010-03-05 08:09 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
a sample project illustrating the issue (147.66 KB, application/x-compressed)
2009-06-10 08:03 UTC, akochnev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description akochnev 2009-06-10 08:01:08 UTC
When I create groovy classes (e.g. domain classes, controllers, etc), there is no code completion for their methods
inside other Groovy classes that use them (e.g. I'm writing a unit test that uses the domain class). In contrast, if I
create a Java class inside of src/java, code completion for the methods of the java classes is available. 

Similarly, in the import statements, there is no code completion for imports of Groovy classes in packages , whereas
there is completion for Java classes in packages.
Comment 1 akochnev 2009-06-10 08:03:27 UTC
Created attachment 83380 [details]
a sample project illustrating the issue
Comment 2 akochnev 2009-06-10 08:20:33 UTC
In the example project : 

public void foo() {
        
        Monkey m = new Monkey();
        // code completion works here, Groovy class in default package
        m.abcd();
        
        Donkey d = new Donkey()
        // code completion works here, Java class
        d.doNothing()
        
        BarDonkey bd = new BarDonkey();       
        // code completion doesn't work here, Groovy class in a package'
        bd.doSomething();
    }

I poked around the source, I checked out the project metadata and the project seems to contain all the right places in
the classpath (e.g. the source roots). Any tips of what the classpath/completion infrastructure needs to recognize
Groovy classes in packages ? 
Comment 3 akochnev 2010-03-05 08:09:40 UTC
This has been working for a while now.