Fix for broken integration test
Fixed line length in release notes
Replace illegal characters with '?' placeholder.
Updated wrapper to new snapshot.
Configuration-on-demand - cherry-picked a commit from master. It includes some minor fixes, refactoring and bunch of coverage.
Configuration-on-demand - cherry picked from master. Corrected the handling of the default tasks in the COD mode. Now the default project is evaluated just like the root project is. After this change I think the COD is announcable as incubating.
Highlighted TestNG report improvments in the release notes.
Fixed line length in release notes in one place to avoid validation failure.
Prefer using JVM system properties over command line opts, and using GRADLE_OPTS over passing sys props on command line, to make int testing on Windows safer.

The Java ProcessBuilder API on Winblows doesn't deal with CLI arguments with spaces in them (e.g http://bugs.sun.com/view_bug.do?bug_id=6468220). This change reduces the likelihood of running into such issues.
Make ivars of AbstractGradleExecuter private.
Some tweaks to the build types, notably introducing a "sanityCheck" to be the very first pipeline step.
Rework the environment (in the general sense) augmenting for in process int testing to fix bug with gradle user home specification.
Include MavenPublication.from in the DSL docs
Test cases for 'customise maven artifacts' use case
Some spec updates.
Some spec updates.
Add a workaround for GRADLE-2625; specify -Duser.home on the CLI for the daemon executer.
correct variable name.
GRADLE-2023 - actualize the task containers of all subprojects as well as the root project for the 'tasks' task.
Run “codeQuality” tasks for “sanityCheck” build type.

This was always supposed to be part of it (accidentally left out).