Changes between Version 6 and Version 7 of QuickStart


Ignore:
Timestamp:
Feb 8, 2011, 9:35:47 AM (10 years ago)
Author:
jannekevdp@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QuickStart

    v6 v7  
    1414 * By default, the gscf-[version]-test.war download will use an in-memory database, which means that the database is emptied and filled with some example data at each restart. You can specify a database by creating your own configuration: create a file .grails-config/test-gscf.properties in the home directory of the user that runs the servlet container process (probably 'tomcat'). See Configuration below.
    1515
    16 See for more details the INSTALLATION file that comes with the downloaded version, or Database/Production below.
     16See for more details the INSTALLATION file that comes with the downloaded version, or Database/ Production below.
    1717
    1818=== First time run from command line ===
     
    4747=== Use a development environment ===
    4848
    49  * The best free IDE out there for Grails seem to be SpringSource Tool Suite and NetBeans at the moment. Make sure to use the latest version, as Grails support is still much under development. Blog post http://www.grailsblog.com/archive/show?id=15 shows how to get NetBeans and Grails working. Another editor with excellent (and paid) Grails support is IntelliJ.
     49 * The best free IDE out there for Grails seem to be Springsource Tool Suite and Netbeans at the moment. Make sure to use the latest version, as Grails support is still much under development. Blog post http://www.grailsblog.com/archive/show?id=15 shows how to get Netbeans and Grails working. Another editor with excellent (and paid) Grails support is IntelliJ.
    5050 * Checkout the gscf trunk from subversion in a new folder (https://trac.nbic.nl/svn/gscf/trunk)
    51  * Open the folder in the Grails-enabled NetBeans, it should recognize the Grails project
     51 * Open the folder in the Grails-enabled Netbeans, it should recognize the Grails project
    5252 * You might have to change your launch configuration to include the VM parameter -XX:MaxPermSize=256M if you run into PermGemSpace errors
    53  * Launch it from NetBeans (just press the green button ;-))
     53 * Launch it from Netbeans (just press the green button ;-))
    5454 * If this is a first time checkout and launch, you might get dependency errors. This can be resolved by running 'grails run-app', 'grails upgrade --non-interactive', and then 'grails run-app' to run the application again.
    5555
     
    6464=== Grails plugins ===
    6565
    66 When you run 'grails run-app' (as NetBeans does behind the scenes), grails automatically installs any plugins on which the application is depending. To view which plugins are in your Grails cache, run:
     66When you run 'grails run-app' (as Netbeans does behind the scenes), grails automatically installs any plugins on which the application is depending. To view which plugins are in your Grails cache, run:
    6767{{{
    6868ls ~/.grails/1.1.1/plugins
    6969}}}
    7070 * As of Grails 1.3.1, the plugin structure has changed, and this causes sometimes 'plugin not found' errors even on a fresh Grails download and project checkout. Try running 'grails upgrade', that should solve the problem.
    71  * It seems that NetBeans sometimes has trouble installing the Nimble plugin, so if it's not there (grails-nimble-0.3-SNAPSHOT.zip), try running 'grails run-app' from the command line in the application directory.
     71 * It seems that Netbeans sometimes has trouble installing the Nimble plugin, so if it's not there (grails-nimble-0.3-SNAPSHOT.zip), try running 'grails run-app' from the command line in the application directory.
    7272 * Also, if you get complaints about a certain plugin when building from scratch, it could be that some of the plugin versions were are using (see 'application.properties' in the project root) are outdated. Since Grails automatically fetches the newest version of any plugin when installing from scratch, this causes 'artefact not found' errors. You can check for plugin updates with the command 'grails list-plugin-updates'. One way of solving this problem is to upgrade the project plugin version to the newest available version (preferably only latest stable, no RC's), either by updating the version number in 'application.properties' or by using the install-plugin command, e.g. 'grails install-plugin webflow 1.2.2'.
    7373