jetty standalone plugin

This means, all you need todo is to run

java -jar APPNAME.war

and the application will start up and be accessible at

localhost:9090

To compile the application as a standalone application, you need to install the plugin first and run the script

grails "-Dgrails.env=standalone" createStandaloneWar

This also means you need to provide a database configuration for the standalone environment!

why should I use this?

recently I developed a lot of little web application, which I did not want to deploy on a dedicated server. I just wanted to use them as a proof of concept and give them to clients or coworkers to play with them locally. For this it was the best idea to just have a single war file, without any need of installation or configuration

how do I configure my datasource now?

this plugin needs to be run in a custom environment, called 'standalone' for this you need to edit you datasources.groovy file and add a section

standalone {
        dataSource {
            dbCreate = "update"
            url = "jdbc:hsqldb:file:standalone;shutdown=true"
        }
    }

does this plugin interfere with my normal build cycle?

To avoid any issues with existing build cycles and configuration, we decided to generate a custom environment for this reason. So far it has only be tested in a couple of applications, so please provide us with some feedback.

do you have some examples of applications, which are using this plugin?

we are working on releasing a couple of applications. Please be patient.

does it really require grails 1.3.5?

I honestly have no idea, please test if it runs with older version. We are only developing with 1.3.5+. If you test it, be so kind and adjust the version requirements.

why do I have to specify the environment every time, can't the script set this?

we are still trying to figure this one out, but right now this is sadly required. We hope to avoid this in future releases.