maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Commented: (MINVOKER-7) Add groovy support for pre/post build hook scripts
Date Thu, 15 May 2008 18:29:27 GMT


Benjamin Bentmann commented on MINVOKER-7:

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
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?

> Add groovy support for pre/post build hook scripts
> --------------------------------------------------
>                 Key: MINVOKER-7
>                 URL:
>             Project: Maven 2.x Invoker Plugin
>          Issue Type: New Feature
>            Reporter: Arnaud Heritier
>            Assignee: John Casey
> I would like to be able to write those scripts in groovy instead of beanshell. I suppose
that it is possible. We could reuse the code of the maven plugin to execute groovy scripts
(groovy-maven-plugin @ mojo).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message