Details
-
New Feature
-
Status: Closed
-
Critical
-
Resolution: Duplicate
-
None
-
None
-
None
Description
Can we have a way to opt-out of Groovy objects as there is an overhead of the MetaClass? These can be tagged as @JavaClass or @NoMeta.