[GRADLE-2945] Adding exclusions in generated pom
[GRADLE-2945] Adding exclusions in generated pom ( checkstyle build fix)
Replace tab with spaces (style fix)
Removing `lib` and `bin` directory checks from distributions installation. Checks to not reflect the actual expected output of a distributions installation (which is anything).
First story for Google Test support: Specific class type for CUnit binary
Added design doc for testing on native runtime
Merge pull request #274 from ffos:GRADLE_2945
Minor improvements to maven-publish exclusion support

- tabs to spaces
- Added test fixture type for MavenDependencyExclusion
- Avoid unnecessary collection empty checks
Handle wildcard excludes when publishing with maven-publish
Release notes for `maven-publish` improvements
REVIEW-5008: Update spec based on updates to ‘unified configuration model’ spec
A bit more detail for the dependency-management spec
Added some open issues to spec.
Fixed typo.
Merged older 'building-multiple-outputs-from-jvm-languages' spec into 'dependency-management-for-jvm-components' spec.
Merged older 'non-jvm-languages' spec into 'dependency-management-for-jvm-components' spec.
Moved some open issues down to the end of the spec, and categorise the open issues to some degree.
Split bigger story into 2 smaller ones
Should remember to preview before commit...
Remove Groovy jars duplication in generated project

Generated sample Groovy project uses groovy.jar (core) while some
dependencies (like Spock) have groovy-all.jar as a transitive
dependency. Gradle treats them as different libraries and there is
a warning about duplicated classes (like AST transformations) during
compilation.
This commit adds global (for all configurations) rule to replace all
modularized Groovy jars with groovy-all artifact.