Details
-
Bug
-
Status: Open
-
Critical
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Symbols resolved for annotations are inspected using ClassNode.getTypeClass() called on the annotation's type. This attempts to load annotation class into JVM.
If the referenced annotation is in the same project, the classes may not be generated yet an the j.l.Class cannot be loaded. The compilation immediately terminates with an internal error, bypassing rest of attributing work.
References to library annotations are OK - they are loaded from .class files (althoug loading into JVM should be avoided)
Note: this is a Groovy bug, not NetBeans. Must be fixed in Groovy, or we need to patch Groovy for our purposes.
Attachments
Issue Links
- is related to
-
GROOVY-10231 Groovy compiler loads user project class into JVM
- Open
- relates to
-
GROOVY-9719 Class loading issue when class has annotation referenced to a nested class
- Open
-
GROOVY-4156 [greclipse] Can we make ClassNode a less leaky abstraction?
- Open