Commits on May 17, 2012
Commits on Feb 14, 2012
Commits on Jan 9, 2012
  1. The previous message "Cannot ask for input when --non-interactive fla…

    bond- committed Jan 9, 2012
    …g is passed. You need to check the value of the 'isInteractive' variable before asking for input" confuses the user.
Commits on Jul 13, 2011
  1. also populate args property from CommandLineParser

    Graeme Rocher Graeme Rocher
    Graeme Rocher authored and Graeme Rocher committed Jul 13, 2011
Commits on Jun 29, 2011
  1. Merge pull request #71 from wholegroup/fix

    graemerocher committed Jun 29, 2011
    small fix
Commits on Jun 20, 2011
  1. revert to the old "install" task which sets the development workspace…

    jeffbrown committed Jun 20, 2011
    … root up as a valid GRAILS_HOME
  2. rework the install target so that it creates an install/ directory at…

    jeffbrown committed Jun 20, 2011
    … the top of the workspace and sets that up as a valid GRAILS_HOME
Commits on Jun 18, 2011
Commits on Jun 17, 2011
  1. bug in confirmInput

    wholegroup committed Jun 17, 2011
Commits on Jun 16, 2011
  1. renamed 'console' binding variable to 'grailsConsole' since it confli…

    burtbeckwith committed Jun 16, 2011
    …cted with the 'console' target in Console.groovy
Commits on Jun 11, 2011
  1. whitespace, warnings, deprecation fixes, switched from StringBuffer t…

    burtbeckwith committed Jun 11, 2011
    …o StringBuilder where possible
Commits on Jun 9, 2011
Commits on Jun 3, 2011
Commits on May 28, 2011
Commits on Nov 29, 2010
Commits on Nov 26, 2010
  1. Improve performance of script load times, package static resources as…

    graemerocher committed Nov 26, 2010
    …ynchronously, refactored some script code into classes
Commits on Sep 24, 2010
Commits on Jun 22, 2010
  1. cleanup

    burtbeckwith committed Jun 22, 2010
Commits on Feb 21, 2010
Commits on Feb 20, 2010
  1. GRAILS-5571 - support verbose compilation.

    ldaley committed Feb 20, 2010
    This can be done via the CLI arg “-verboseCompile” or by setting the “grails.project.compile.verbose” build setting. The CLI arg takes precedence.
Commits on Feb 19, 2010
Commits on Dec 14, 2009
  1. handles script setting of BuildScope better (by using toUpperCase() b…

    graemerocher committed Dec 14, 2009
    …efore calling valueOf())
Commits on Dec 4, 2009
  1. fix for GRAILS-5475 "Legacy system-property-setting gets …

    graemerocher committed Dec 4, 2009
    …overwritten in any case, even if is not given"
Commits on Nov 13, 2009
  1. Grails no longer creates eclipse, intellij, textmate or ant build fil…

    graemerocher committed Nov 13, 2009
    …es by default. Instead there is a new integrate-with script that accepts different arguments like --ant, --textmate etc.
    The integrate-with script is extensible through the build system
Commits on Nov 6, 2009
  1. initialize build settings before configuring default paths otherwise …

    graemerocher committed Nov 6, 2009
    …you get null application name/version
Commits on Oct 29, 2009
Commits on Oct 5, 2009
  1. Interactive mode can survive scripts calling exit() again. This was

    pledbrook committed Oct 5, 2009
    broken when GrailsScriptRunner was converted to Java.
Commits on Sep 23, 2009
  1. When I removed _GrailsInit as a dependency of _GrailsCompile, some of

    pledbrook committed Sep 23, 2009
    the commands broke. The underlying problem was that I had always intended
    for _GrailsInit to be low in the script hierarchy, with only the end-use
    scripts depending on it. However, it had some critical closures and
    properties (such as 'exit' and 'logError') in it. These should have
    been moved into a script further up the hierarchy a long time ago, but
    better late than never.
    So, 'exit' et al. have been moved to _GrailsSettings, and the checkVersion
    target has been moved to _GrailsPackage. Not sure that's the ideal place
    for it, but good enough for now I think.
  2. This ostensibly fixes a problem with the _GrailsWar script which was

    pledbrook committed Sep 23, 2009
    using the wrong signature for one of the PluginBuildSettings methods.
    I also took the opportunity to change as much code as possible to use
    PluginBuildSettings directly, rather than GrailsPluginUtils. In two
    cases (DevelopmentResourceLoader and GrailsCompiler) this wasn't easily
    done, so they still call into GrailsPluginUtils. Because of that, the
    _GrailsSettings script now creates the PluginBuildSettings instance and
    uses it to initialise GrailsPluginUtils.
Commits on Sep 11, 2009
  1. moved servertPort settings back to _GrailsSettings as it may be neede…

    graemerocher committed Sep 11, 2009
    …d by client tools like functional test frameworks etc.