Refactored out some dependencies on Ivy, further refined the implementation of Aether with support for including framework dependencies, excludes etc.
fix compilation error and failing test
additional test for exclusion of framework dependencies
introduce common interface (DependencyManager) for both ivy and aether to implement and refactor ivy setup code out of BuildSettings.
Initial round of refactoring and integration work to get Aether setup as the dependency resolver within Grails. Abstracted Ivy integration away from BuildSettings introducing new interfaces (DependencyManager, DependencyReport etc.) that both Ivy and Aether implement.
Clean up the POM modifications so that they are made to all POMs, not just the uploaded ones.
Treat the “dist” dir like an m2 repository for the core jars, instead of just copying the jars there in a flat fashion (i.e. without metadata).
don't use unique version for jars, flatten the home directory to avoid breaking backward compatibility 
update RepositoriesConfigurer to use the POMs from the dist directory for resolution
Aether: Added support for 'build' scoped dependencies and checksum policy config
Aether: split out plugin zips and jars in the dependency report
fix dependency pattern for grailsHome()
refactor code to use DependencyManager interface instead of depending on Ivy
Aether: bootstrap Aether from starter.conf file inside its own class loader and use to resolve dependencies. Dependency resolution with Aether is now working in a Grails application. There are some issues with plugin uninstallation which are being worked on.. stand by...
Aether: various fixes around plugin uninstallation (although still broken)
missing from last commit
GRAILS-9458 Better test duration units

Displays the test duration in minutes and seconds rather than milliseconds.
Aether: fix issue populating plugin dependency zip files
reduce default log level for simple logger binding
Refactor UAA to not introduce dependencies into framework and isolate classloader from rest of framework. Now protobuf etc. can be removed as build dependencies and UAA doesn't have to be a direct dependency of Grails itself (which causes problems with Maven because UAA is not in Maven central)