Introduce CacheValidator
- Allows Cache specific (in)validation logic.
- CacheValidator can be used to add validation logic for a Cache.
- CacheRepository scoped cache can still be triggered via CacheUsage.REBUILD.
Introduce --recompile-scripts commandline option.
- Recompiles build scripts without cleaning the whole cache repository.
- Deprecate --cache... commandline option.
- Add unittests for --rerun-tasks, --recompile-scripts and --refresh-dependencies.
Add some javadoc to new StartParameter options
Made sure the temp dir is unique even when we access the temp dir in setup() method. This should help solving some mysterious failures we had on the CI.
GRADLE-2163 - don't generate alternative boolean getters for Booleans, and only generate the alternative if a method exists with that name.

Groovy doesn't add the “get” variant for Boolean properties (only boolean) as the “is” convention is not valid for objects.
Merge branch 'GRADLE-2163'
GRADLE-2163 - integration test for convention mapping primitive booleans.
imports.
GRADLE-2149: release and rc task now depend on java7
- checkJavaVersion now checks that java7 is current Jvm
- add checkJavaVersion dependency to rc task
- add todos to fail early on wrong jvm and don't depend on task names (alphabetical order)
rename CopyTaskPermissionsIntegrationTest to ArchiveTaskPermissionsIntegrationTest as copyTask is not tested here
GRADLE-971: Add integration test to show that issue is not yet fixed
GRADLE-971: Add integration test for simple copy action
GRADLE-971: renamed CopyTaskPermissionsIntegrationTest to CopyPermissionsIntegrationTest
GRADLE-1974 eclipse wtp plugin adds the web libraries classpath container. Initial stab at the implementation. Details:

-The benefits of the container include: nicer view of the dependencies; we avoid getting out of sync between the classpath dependencies and the dependencies that are deployed; we allow quick drop-in of dependencies should someone want to try something out quickly and put jars in webapp/WEB-INF/lib; natural approach for teams that use WEB-INF/lib to manage dependencies. Also if the container is a good approach we can at some point remove some workarounds we have for mitigating eclipse warnings regarding exporting dependencies, etc.
-By default the container is turned off. The reason is following: for the container to make any sense I need to remove explicit entries from the .classpath metadata. This way the container actually manages the dependencies and it uses entries from WTP component metadata files. However, this is a change in the behavior and there might be some cases I don't know yet about that warrants the classpath entries. To avoid big bang change for wtp users, the container behavior is 'off' by default.
-Added a very simple dsl to configure the web libraries container. It needs reviewing so it's dead simple at the moment. The configurability includes basic stuff like the container name, exported/unexported, on/off, replacing .classpath entries on/off. In theory, this should also be useful for ear + wtp, as ear also can use a container (a different container, though).

Pending: cleanup & documentation.
GRADLE-1974 eclipse wtp web libs container: handled the case of the same container mentioned twice.
GRADLE-1974 eclipse wtp web libs container: handled the case when someone tries to use a container without war plugin applied. Without war, the container should be configured manually. It should be useful for ear guys, should they need to use the 'EAR libraries' container. Refactored the wtp plugin slightly so that it configures the EclipseLibrariesContainer (better clarity).
GRADLE-1974 eclipse wtp web libs container: added very simple docs for the EclipseLibrariesContainer. Since I need to review that stuff anyway I don't want to write too much docs for further rewriting :)
The CI build no longer runs *all* compatiblity tests. There are separate CI jobs for that.
Merge branch 'pull-request-74'
Added a way of running cross versions tests only. Created convention for the cross version tests to alway contain 'CrossVersion' in the spec name. This convention is enforced by validation in the Runner. The goal is to enable way of running cross version tests in a separate suite in CI.