ProjectLayoutIntegrationTest.groovy

Changing Groovydoc integration tests to run in their own daemon and own gradle user home.

+review REVIEW-5677

Upgrade to Groovy 2.4.4

+review REVIEW-5598

specify -XX:MaxPermSize=512m for ScalaCompile tasks in integtest - add forking option - also specify option in ForkScalaCompileInDaemonModeFixture - another attempt to fix PermGen failures in coverage builds

specify -XX:MaxPermSize=512m for ScalaCompile tasks in integtest - attempt to fix failing coverage build

update library versions in samples and integtests

- update slf4j + ant in samples

- groovy in samples + integtests

+review REVIEW-5443

Upgrading samples and integration tests to Groovy 2.3.9

+review REVIEW-5372

revert accidently changes on integTests

+review REVIEW-5251

Force another test that compiles scala to fork the compiler when running with the daemon.

+review

Update Groovy version used in samples, and in integ tests for 2.3.x to 2.3.6.

+review REVIEW-5055

Upgraded a bunch of things to Groovy 2.3.3

Updated some samples and tests to use newer Scala version.

Changed some samples and tests to use newer Groovy versions.

Changed some int tests to use DefaultTestExecutionResult rather than JUnitTestExecutionResult, to use whatever the default mechanism for verifying test results happens to be.

GRADLE-2744: when setting ProjectDescriptor#projectDir use FileResolver instead of just canonicalising the parameter.

Remove RuleHelper.

Use constructor injection instead of reflection.

REVIEW-1033: rename DefaultTestExecutionResult to JUnitXmlTestExecutionResult

Some renaming and cleanup around the test/temp directory used in tests.

REVIEW-867: Rename test fixture JUnitTestExecutionResult -> DefaultTestExecutionResult.

update default library versions used in tests and samples

- JUnit -> 4.11

- Groovy -> 2.0.5

- Scala -> 2.9.2

- use short instead of long dependency notation

- eliminate usage of `scalaTools` configuration

Moved code related to GradleExecuter and GradleDistribution into org.gradle.integtests.fixtures.executer - Affects many, many files, but mostly just imports - Certain files (eg RuleHelper) are not in the correct spot, but were moved to avoid cycles

downgraded Scala samples and one integration test to Scala 2.9.1 because in 2.9.2, scaladoc requires Java 1.6 (probably a scaladoc bug)

updated samples and tests to use latest released scala version

Refactoring and restructruization. Moved the samples integ tests into a spearate package for better visibility and runability. Moved test fixture code into the integ test internal subproject.

Refactoring - moved some non-test classes to a separate package

Use maven central only to get scala compiler.

Updated samples and int tests to use repositories.maven() instead of mavenRepo().

Separated classes ouput directory from resources output directory. This requires a code review but I preferred to check in the changes. Updated the documentation, user guide and tests accordingly. New property is called resourcesDir (I somewhat don't like the name but that's what we agreed with Adam).

GRADLE-1355 - Move integration tests out of core project and into their own integTest project.