updating classpath during installation might fail for an unknown reason.
Therefore, make the process more robust by wrapping up in try-catch block
and ignoring a potential error. This can have effect only when
the plugin installation is part of a grails tasks that requires
code compilation and could be work arounded by invoking
grails refresh-dependencies first
fixed resolving validation-api source jar via grails 2 dependency manager:
instead of specifying ivy configuration at resolving process,
use m:classifier extra attribute at ModuleRevisionId
Fixes dependencies resolving for gwt 2.5.1
run-gwt-codeserver should get only the list modules with entry point defined
Merge pull request #17 from dawsonsystems/source-dependencies-fix

Source dependencies + Install fix
Merge pull request #18 from dawsonsystems/gwt2.5.1-dep-fix

Fixes dependencies resolving for gwt 2.5.1
Merge pull request #19 from dawsonsystems/codeserver-modules-with-entry-points

run-gwt-codeserver should get only the list modules with entry point def...
bump to 0.9-SNAPSHOT
Merge branch 'master' of github.com:dawsonsystems/grails-gwt
Added possibility to specify module when running codeserver
[GPGWT-106] Don't expose spock/ release plugins to the outside world
Merge pull request #22 from smithimage/master

Added "module" argument to script run-gwt-codeserver
Merge branch 'master' of github.com:dawsonsystems/grails-gwt
[GPGWT-103] Do a type check before assuming string.
[GPGWT-93] Error message when no modules are available and run-gwt-client is invoked.
[GPGWT-116] Fix typo
Git ignore attempt to remove web-app
[GPGWT-111] Ensure we don't bundle any default grails web artifacts.
Needs a comma!
[GPGWT-109] Remove gwt-dev and gwt-user from the deps that will mean they end up inthe war.
So, removing them from the war file.