Using groovy scripts in your application deployment
DZone's Guide to
Using groovy scripts in your application deployment
Join the DZone community and get the full member experience.
Join For FreeVerify, standardize, and correct the Big 4 + more– name, email, phone and global addresses – try our Data Quality APIs now at Melissa Developer Portal!
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 $*
Developers! Quickly and easily gain access to the tools and information you need! Explore, test and combine our data quality APIs at Melissa Developer Portal – home to tools that save time and boost revenue. Our APIs verify, standardize, and correct the Big 4 + more – name, email, phone and global addresses – to ensure accurate delivery, prevent blacklisting and identify risks in real-time.
Like This Article? Read More From DZone
Topics:
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}