adityaanikam commented on issue #742: URL: https://github.com/apache/maven-invoker-plugin/issues/742#issuecomment-5190312316
Looked into this against current master. Searched the plugin's own source for any explicit Groovy compiler target configuration (`CompilerConfiguration`, `GroovyShell` setup with a target bytecode version) and found none, which is consistent with your read: nothing in this codebase sets a target bytecode level for `verify.groovy`, so Groovy falls back to its own default of targeting whatever JDK is currently running it. I was not able to locate the exact class that constructs the Groovy engine yet, since it may live in a shared dependency rather than directly in this plugin's own module, so I have not confirmed the precise call site. I would like to work on this. Next step is finding exactly where the Groovy engine gets constructed for `.groovy` script execution, then threading the existing `maven.compiler.release` value used elsewhere in this plugin into that configuration. Will confirm the exact class and line before proposing a diff, since I do not want to guess at a fix location I have not verified. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
