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 8 Next »

A Windows-specific installation script

that allows to create installers for the different groovy versions. You can examine the results on the download page.

The installer first copies the groovy files to where the user wants,

then asks for permission to create a variable GROOVY_HOME and to add the respective bin directory (%GROOVY_HOME%/bin) to the path, if no reference to groovy already exists in it.

The user can decide whether to put these into the user or system environment (on Win 95 and Win 98 this information is appended to the autoexec.bat instead) i.e., whether the installation will be for the current user or for all users.
Then the installer checks for the existence of JAVA_HOME. If it doesn't exist, a message box points out the potential problem. 

Next the user can decide whether or not to install the native launcher,

and finally  the user can decide whether to associate .groovy files with the native launcher.

As you can see in the screen shots, currently english, german, french and spanish are supported as installation languages. 

Working with the installer source

To use the installer source to create your own binary installers, simply check it out into an Eclipse workspace. Additionally you might want to install the NSIS-Eclipse-Plugin, it helps when developing NSIS stuff.

If you have worked with NSIS-scripts already there should be no big problem understanding what is done.

The main script is the file setup.nsi, where you can find the installer program. Three additional pages are defined, Variables, NativeLauncher and FileAssociation, and for each you can find the respective .ini file containing the screen placement. Simply open them in the design editor provided by the Eclipse-Plugin, and you can see what they look like.

Two bmp-images contain the Groovy logo in different resolutions, one for the welcome page and one as header image for the other pages. The name is the game ...

Fínally you have the launch scripts. These actually start the compiler with different settings for the groovy version, the groovy location (on your hard disk) and the location of the native launcher. The groovy version influences the final name of the installer.

The launch scripts are setting the following variables:

SOURCE_VERSION defines the version of the release
SOURCE_DIR     is the full path to the groovy install directory
NATIVE_DIR     is the full path to the native launcher

Most probably you only have to set these variables and you are happy to go.

Have fun.

If there is any problem whatsoever, either ask on the mailing lists or contact the author at

  • No labels