Hi Eric,
1. The idea of maintaining one File with command separated values is ok if
the classes are few (in 4 or 5). If we plan to write lot of Extension
Classes, then that single file is becoming un-manageable
2. If repo is branched, then same file is touched by more people with their
own entries
By having a annotation processor, we can update the
org.codehaus.groovy.runtime.ExtensionModule file with required entries
during compilation time...
Having said that I will be happy if we have some arrangement like this...
1. We will have below directories in classpath
a. META-INF/groovy/ex
Let me ask this for clarity. Are your extension classes written in Java or
Groovy or a mix? Annotation processor is a Java compiler mechanism. Groovy
compiler uses local AST Transforms to similar effect.
If you are writing Java classes with the intent of providing additional Groovy
support,
So far we have only Java Extension classes.
With AST Transformation, can we register Extension classes with Groovy
Runtime?? is it what you are saying?
-
Thanks,
Adithyan K
India
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
On 20.06.19 20:13, adithyank wrote:
So far we have only Java Extension classes.
With AST Transformation, can we register Extension classes with Groovy
Runtime?? is it what you are saying?
The AST Transformation can write to the extension module file, which the
runtime uses to register the exte
