Use debug instead of warning level for these.
GRADLE-2187: Add a more helpful error message to Jdk6Compiler when executed within a JRE and no JDK installed.
GRADLE-2187 remove unused imports
Prepare for next version
Cherry picked user guide/dsl reference fixes I recently made in master. Mainly fixed references to old api, some updates to daemon/build environemnt in the guide.
converted to spec.
GRADLE-2232 - Add expectantly failing test for NoClassDefFoundError: junit/framework/TestCase
fixed GRADLE-2232: TestCase not found on compile classpath in rc-1

- updated code comments and added some tests
fixed typo
fixed typo
improvements and fixes to DaemonForkOptions/ForkOptions/GroovyForkOptions

- made CompilerDaemonManager respect jvmArgs
- removed obsolete code from ForkOptions
- added GroovyForkOptions.jvmArgs (necessary in order to be able to debug ApiGroovyCompiler)
- made DaemonForkOptions retain order of several list-like properties (by using LinkedHashSet instead of HashSet)
- added tests
improved fix for GRADLE-2232: TestCase not found on compile classpath in rc-1

- became necessary because previous fix broke all transforms written in Groovy
- copied and modified Groovy's JavaAwareGroovyCompilationUnit to solve the problem that this class doesn't allow to set transformLoader like CompilationUnit does (setting this field reflectively wouldn't work because it's already used in the super constructor)
- changed ApiGroovyCompiler to use our JavaAwareGroovyCompilationUnit
- added tests
- modified samples/groovy/groovy-1.5.6 to use groovy(Test)Compile.groovyOptions.useAnt = true (ApiGroovyCompiler now requires Groovy 1.6 or higher)
GRADLE-2226, LongRunningOperation.withArguments() not working. The arguments parsing now happens with allowUnknownOptions(). Also the verboseLogging settings is consumed differently - we always parse the arguments regardless of the verboseLogging. This way we can avoid such bug in future. The verbose logging parameter only kicks in if the log level is not provided by the arguments. Minor tweaks to the integration test.
Refactored a bit the prepareVersionsInfo task so that it's cleaner and its behavior is more conventional.
GRADLE-2226, LongRunningOperation.withArguments() not working.

The arguments parsing now happens with allowUnknownOptions(). Also the verboseLogging settings is consumed differently - we always parse the arguments regardless of the verboseLogging. This way we can avoid such bug in future. The verbose logging parameter only kicks in if the log level is not provided by the arguments. Minor tweaks to the integration test.

(cherry picked from commit 4c9ea8e)
Scaled down the dynamic properties deprecation warnings.

 The idea is to balance out usefulness with tidyness, especially for the large multi-project builds that configure a lot properties in allprojects/subprojects {}. The main driver are the outputs from some client's builds were those deprecations take dozens of screens, sometimes even taking 90% of the entire build output. Details:

-The url and a generic message is printed only once, regardless of the number of properties.
-The warnings are not repeated for the same property on the same type. If there are more properties with the same name on the same type we print a generic information about it (in majority of cases it means the property is created in subprojects {} scriptblock).
-The value is abbreviated to the first 25 chars to avoid printing some humongous objects (another use case from the client's).

Pending: The DeprecationLogger needs refactoring (probably on the master, though).
Merge branch 'release'
Removed an extra line in the deprecation message for dynamic properties.
Removed an extra line in the deprecation message for dynamic properties. (cherry picked from commit 4418eb1)
Refactoring in the ExecHandle stack after accommodating the daemon use case. First step. Placed the streams forwarding/draining complexity in a separate object.