Grails: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
* If you write your own Gant scripts (in $PROJECT_HOME/scripts), you can apparently completely customize the build process. | * If you write your own Gant scripts (in $PROJECT_HOME/scripts), you can apparently completely customize the build process. | ||
* Note that when running the embedded Jetty server (or when running any Grails script for that matter), the additional JAR dependencies are loaded. | * Note that when running the embedded Jetty server (or when running any Grails script for that matter), the additional JAR dependencies are loaded in the classpath. | ||
== Questions == | == Questions == | ||
Revision as of 13:57, 17 May 2007
Grails is a next-generation web development framework powered by Groovy and Java technologies.
Dependencies
- Grails use the embeddable Groovy jar. You will run into problems if you use the standalone Groovy jar.
- Grails use currently as of 0.5.0 a custom build of a Spring-modules snapshot. You must thus use the .jar provided in Grails distribution.
- Grails use version 2.1 of commons-lang.
Deployment and build system
- Under the hood, Grails uses Gant as its build system. Gant is based on Ant but allows you to write build files with Groovy code: you are no longer restrained to XML programming!
- If you write your own Gant scripts (in $PROJECT_HOME/scripts), you can apparently completely customize the build process.
- Note that when running the embedded Jetty server (or when running any Grails script for that matter), the additional JAR dependencies are loaded in the classpath.
Questions
- Does scaffolding works on deployed environment or only on the test container?
- How to package a WAR file for deployment on a servlet container, and customize the process?