This installment of Gradle Glam is not about a particular plugin or Gradle trick. Rather it discusses some features that I think will benefit the overall Gradle community. Some of these features might be already in the works by the fine folks at Gradleware, some others are ... up for grabs I guess 
In no particular order these are:
- The maven-publish plugin should honor the compile/runtime configuration when setting the value of <scope> for each dependency added to the generated pom. Test dependencies should be discarded/hidden. Currently all dependencies have runtime as their scope.
- Centralized metadata that can be consumed by several plugins, for example project URL, contributors, developers, etc. This information can be consumed b maven-publish, bintray and other plugins. Netflix already provides a set of plugins that deal with this problem up to some extent.
- Integrate reporting plugins with reporting capabilities provided by the build-dashboard plugin. For example stats, license and versions plugins.
- A plugin that generates prettified HTML source with links, much like Maven's JXR.
- Aggregated documentation and reports, much like Maven's site feature. Bonus: use Asciidoc as the defacto format.
- Environment aware build file variations via a DSL. Think applying ConfigSlurper's environments feature to a build file, but more open (not just environments but platforms or other constrained vars).
Keep on Grooving!
