Use a closure for the classpath for extractAnnotations task

    The extractAnnotations task used to set the classpath in the task creation code
    which happens before the Android SDK has been set. Therefore the renderscript
    support was not available and the classpath was incomplete.

    Instead, use a closure to set the classpath which will be re-evaluated each
    time the classpath is looked up. By the time the task actually executes,
    the SDK has been set and the classpath is set correctly.

    BUG=72652

Change-Id: I93d3d68048b935cdb9360c7403322e379e93ea0a
Merge "Use a closure for the classpath for extractAnnotations task" into idea133-milestone
Made placeholders field common to build types and build flavors.

Up to now, users could only specify placeholders values in the build flavors
part of the build.gradle.
With this change, placeholders values (with the same syntax) can also be
specified in the build type declaration. The build type value will always
override build flavor values for the same key.

Change-Id: I35016a520666bd5f0ae487ffa81cf9a12711c069
Merge "Made placeholders field common to build types and build flavors." into idea133-milestone
Do not fail non resolved placeholder in libraries

When placeholders are not resolved in library files, it is now considered
that the resolution will be provided during application building.
This allows to put placeholders in built library files and have
such placeholders resolved per application.

Change-Id: I6447ba3b3c5bf0f43d1c24e782d8719d3b605294

Conflicts:
	build-system/manifest-merger/src/test/java/com/android/manifmerger/ManifestMerger2Test.java
Merge "Do not fail non resolved placeholder in libraries" into idea133-milestone