cancel
Showing results for 
Search instead for 
Did you mean: 

removing groovy by default?

tombaeyens
Champ in-the-making
Champ in-the-making
currenly groovy is in the default dependencies of the engine.

i think we should try to make that an optional dependency.  maybe we can scan for availability of one of the groovy - jsr 223 engine classes and depending of the outcome add it to our ScriptingEngines.

alternatively we could consider to document how users have to add groovy (just like now we'll have to document how users can add any of the other scripting languages)

that will keep the minimal runtime dependencies even more neat and tidy.  especially since we now have explicit groups of examples showing the runtime and testing dependencies explicit.
2 REPLIES 2

jbarrez
Star Contributor
Star Contributor
I agree.
Do you have a Jira already for updating the docs?

tombaeyens
Champ in-the-making
Champ in-the-making
now there is the jira issue: http://jira.codehaus.org/browse/ACT-163