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.
| Summary: | *Editor* cannot resolve external libs/jars in grails applications. | ||
|---|---|---|---|
| Product: | groovy | Reporter: | runjorel <runjorel> |
| Component: | Grails | Assignee: | Petr Hejl <phejl> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | Macintosh | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
Can you please test the issue with daily build? I can't reproduce it with recent trunk. For me class is resolved in both controller and ordinary groovy class. Actually this is a duplicate of issue 144243. *** This issue has been marked as a duplicate of 144243 *** |
When I add external jars/libraries into my grails application (MyGrailsAppDir/lib), the *editor* cannot resolve any of the classes from those jars. The Grails application runs fine, but with all the LOC I have that use those external libs, all those red-lines make it difficult to debug. Example: import com.testClass.MyOwnObject // This jar has been put in MyGrailsAppDir/lib class AGrailsController{ def index={def a = new MyOwnObject()} } The "def a = new MyOwnObject()" is underlined in red, with a warning saying "Unable to resolve class" When I run the project, everything runs fine! No errors. As I said before, it just makes it difficult to debug. This issue is with NB6.5RC1 I understand it's a very minor issue. Thanks for the groovy/grails support!! It's awesome.