Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Provides a shell-like capability for handling external processes.

Module Overview

Groosh is a unix like shell written in Groovy. It has also been known as the Process Module but was renamed (back) when it was update to work with Groovy 1.0.

The current version of Groosh is 0.1.1

Team Members

  • Yuri Schimke - Founder and original contributor
  • Alexander Egger [alexander.egger at] - Current maintainer



Source and binary releases are available at

A RPM package for openSUSE 10.2 can be installed via the openSUSE Build Service repository


If you use the openSUSE RPM, just install it and you are ready to go.

If you use the binary distribution e.g. (groosh-0.1.1-bin.tar.gz).
Untar it and copy groosh-0.1.1.jar to your $GROOVY_HOME/lib.

Try the following script to check if it worked:

def gsh = new com.baulsupp.groovy.groosh.Groosh();;

Have a look at the examples directory for more examples how to use


Groosh is based on Groovy 1.0. It has not been tested with the latest Beta. Once Groovy 1.1 is out Groosh will move to Groosh 1.1


The following example shows Groosh in action:

Another example :

Sometimes the name of a shell command conflicts with a Groovy method (for example ''grep''). This means that

does not execute the shell command, but the Groovy method grep(...).

As a workaround for that you may prefix any shell command with _ this means the example above becomes


Source Control

The Groosh source code is available from the Codehaus SVN at


Building from the source distribution

Untar/unzip the source distribution file (e.g. groosh-0.1.1-src.tar.gz)

Groosh uses Maven 2 for building. You have to have Maven 2 installed.
Just execute mvn in the groosh directory and groosh-0.1.1.jar gets build
as well as the source and binary distribution.

Building the SVN version

Check out the source from

Building works the same as for the source distribution.


Please contact Alexander Egger [alexander.egger at] by e-mail.


Mailing List(s)

Issue tracker

  • No labels