Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Using groovy scripts in your application deployment

DZone's Guide to

Using groovy scripts in your application deployment

· Java Zone
Free Resource

The single app analytics solutions to take your web and mobile apps to the next level.  Try today!  Brought to you in partnership with CA Technologies

We distribute our application as tar.gz on Linux.
Our server is actually jetty with our web application, but we want to make some checks before the server start in order to provide clear error messages w/o need for a user to scan log files.  So I wrote the server start script in groovy and packed groovy installation (and JRE as well) into the application distribution.
The problem was, however, that groovy script can't run by itself (like shell script), so I wrapped the script into the shell script.

Assuming that our installation looks like
tools/jre
tools/groovy
server/bin/myscript
server/groovy/myscript.groovy
server/groovy/SomeClass.groovy
lib/myjar.jar
the shell script "myscript" will looks like:
#!/bin/sh

server_bindir=`/usr/bin/dirname $0`; 
server_bindir=`(cd $server_bindir;pwd)`; #get absolute path
server_dir=`dirname $server_bindir`;
server_groovy_dir=$server_dir/groovy

install_home=$server_dir/..;
jars_dir=$install_home/lib


JAVA_HOME=$install_home/tools/jre
export JAVA_HOME


$install_home/groovy/bin/groovy -cp $server_lib_dir:$jars_dir/myjar.jar $server_lib_dir/myscript.groovy  $* 

CA App Experience Analytics, a whole new level of visibility. Learn more. Brought to you in partnership with CA Technologies.

Topics:

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}