Checking Projects into SVN - Grails - Confluence

Up to and including Grails 0.4.x there are files that are generated or copied by Grails within your project tree. This can be problematic as it is unclear what is to go into SVN and what isn’t. In addition, you will not usually want your compiled .class files going into version control, nor duplicates of your libs etc.

This is correct at the time of writing (Grails 0.4.x) but makes the following assumptions:

* You do not want ./plugins/core (Core Grails plugins) under SVN
* You do not want anything under ./web-app/WEB-INF/ under SVN. You should not usually need to put files in here. Files from ./conf are copied to WEB-INF/classes so they are on the classpath, if you need to supply anything.

Why is this such a hassle? Well SVN prevents files or directories being considered for version control by checking an “ignores” list that is set via an SVN property. This property is set on specific directories within your SVN working copy. Therein lies the problem - until you have a working copy you cannot tell it to ignore files.

Grails - GrowlGrails

Growl is a generic but slick notification framework for OS X. This script bundle adds configurable notifications for common grails script events, so that for example you can have it automatically pop up a message when your “grails run-app” has completed, or an error has occurred while running a grails command.