fix for GRAILS-10487 "Invalid HTTP Status Code for Grails REST with vnd.error support"
Merge branch '2.3.x' of github.com:grails/grails-core into 2.3.x
fix for GRAILS-10513 "When using Aether all plugin dependencies are compile scope regardless of how they are declared in BuildConfig"
fix for GRAILS-10503 "Code coverage plugin is broken in forked mode due to MissingPropertyException on 'config'"
Test argument to create-multi-project-build for validity.

Fixes GRAILS-10494. If the argument to `create-multi-project-build` didn't
consist of 3 parts separated by colons, the command just threw an exception
when trying to assign the result of `split()` to a tuple. I have added an
explicit check for the 3 parts and simply print a message now and exit if
the number of parts is incorrect.
Fix for GPMONGODB-324
upgrade to aspectj 1.8.0.M1
GRAILS-10448 - remove WebUtils.exposeForwardRequestAttributes
rename protected method
Merge branch '2.3.x'
remove repo.springsource.org/libs-milestone

This has been added as a remote at repo.grails.org for now
Use setMethodTarget to optimize call to getExceptionHandlerMethodFor in controller actions
Merge pull request #404 from sukrit007/GPMONGODB-324

Fix for GPMONGODB-324
fix for GRAILS-10457 - Geb plugin working with forked mode
Add 2 additional repository methods for backwards compatibility with Ivy
Fix for GRAILS-10525 gsp parser always generates a closing tag for namespaced xml elements
Fix for GRAILS-8727: The last class in a *GrailsPlugin.groovy file is treated as the plugin class
Improved fix and test for GRAILS-8727
Updated resources plugin to 1.2.1
Refactor Maven POM generation for consistency.

The number of POMs has now been cut from 5 or 6 to just 2. This makes it much
easier to maintain them and ensure that all generated POMs are up to date. As
part of this refactor, I have also switched from Ant file filtering to Groovy's
SimpleTemplateEngine, which allows for more flexibility in the templates.

There is still a problem in that the `create-multi-project-build` command can't
produce the same POMs in child projects as the `create-pom` command. This is
because you can not get the dependencies of an arbitrary project, only the one
that a command is run in. The best way to fix this is to allow for dependency
resolution on any Grails project, no matter where it is in the file system. And
of course you have to be able to resolve the dependencies for multiple projects
in one JVM instance.