There is a small possible problem in the implementation. In linux you can immediatly execute a groovy script starting with a #!/usr/bin/env groovy Declaration. In windows however you must run java -jar groovy.jar scriptname. So perhaps a workaround is to have only two shell scripts that are platform dependent (e.g. groovy.sh and groovy.bat) which point to the groovy library inside OFBiz and is used to launch all groovy scripts.
I also think groovy.util.CliBuilder might prove very helpful in the implementation Taher Alkhateeb On Aug 20, 2013 10:48 AM, "Jacopo Cappellato" < jacopo.cappell...@hotwaxmedia.com> wrote: > Hi all, > > the proposal is about migrating all the *.sh and *bat scripts to *groovy > scripts: as you know Groovy scripts can be called from the command line and > executed like OS scipts. > The only prerequisite is to have the Groovy jars in the classpath, but > this is easy to implement since it is already included in the OFBiz > distribution. > In this way we could have less platform dependent files and scripts > written in a language that is already widely used in OFBiz. > > What do you think? > > Jacopo > > >
