What is the concern or issue with the comma-separated property in the
org.codehaus.groovy.runtime.ExtensionModule file?
If annotations were used, Groovy would need to scan the entire classpath
looking for tagged classes. The property file allows only looking for a
specific resource in each li
On 19.06.19 17:05, Milles, Eric (TR Tech, Content & Ops) wrote:
What is the concern or issue with the comma-separated property in the
org.codehaus.groovy.runtime.ExtensionModule file?
If annotations were used, Groovy would need to scan the entire classpath
looking for tagged classes. The prope
Okay, that's an interesting twist. If the idea is to have the compiler
generate the ExtensionModule file based on annotations it encounters in Java
and Groovy sources, there may be a path forward to do that. I'm not too sure
how you solve the problem for both Java and Groovy sources. And do y