jira-importer commented on issue #357: URL: https://github.com/apache/maven-invoker-plugin/issues/357#issuecomment-2957782488
**[Benjamin Bentmann](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bentmann)** commented How would you expect the plugin to choose between the BeanShell and the Groovy interpreter (or some future thing) when processing scripts? I could imagine a new mojo parameter "scriptLanguage" that could be set to "beanshell" or "groovy". Would be an explicit hint for the plugin but would limit all IT projects run during the same Invoker execution to use the same script language. Alternatively, some smarter heuristic that simply derives the interpreter from the file extension of the configured pre-/post-build script. In addition, we could consider to extend the mojo parameters "preBuildHookScript" and "postBuildHookScript" to accept extension-less file names and have the plugin search for supported scripts types. For example ```xml <postBuildHookScript>verify</preBuildHookScript> ``` could mean to search for "verify", next for "verify.groovy" and finally for a "verify.bsh", where the first existing one will be picked up. This would allow to easily mix the usage of BeanShell and Groovy among the various IT projects. Thoughts? -- 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]
