DATACMNS-533 - Infrastructure support for SpEL expressions in manually defined queries.

Extracted SPI build for DATAJPA-564 into Spring Data Commons. Simplified the configuration setup code and removed the ability to define a custom EvaluationContextProvider for now. We directly declare a bean definition which automatically picks up EvaluationContextExtensions.

RepositoryFactory(Bean)Support is now aware of the EvaluationContextProvider to hand it to the template method that creates the QueryLookupStrategy. Deprecated the previously existing template method in favor of an extended one.

Removed variable declarations from the extension interface for now as usually properties serve the same purposes as variables which makes the latter superfluous for now. Applied some JavaDoc and API signature polish. Added unit tests for ExtensionAwareEvaluationContextProvider.

Related pull request: spring-projects/spring-data-jpa#101
Related ticket: DATAJPA-564
DATACMNS-533 - Discover declared functions on EvaluationContextExtension.

We new automatically register public static methods declared on classes extending EvaluationContextExtensionSupport as functions to be used within SpEL expressions.

Related pull request: spring-projects/spring-data-jpa#101
Related ticket: DATAJPA-564
DATACMNS-533 - Discover declared properties on EvaluationContextExtension.

We new automatically register public static fields declared on classes extending EvaluationContextExtensionSupport as properties to be used within SpEL expressions.

Related pull request: spring-projects/spring-data-jpa#101
Related ticket: DATAJPA-564
DATACMNS-533 - Support scoping for functions provided by  EvaluationContextExtension.

Added test case for scoped functions.

Related pull request: spring-projects/spring-data-jpa#101
Related ticket: DATAJPA-564
DATACMNS-533 - Expose special parameters in SpEL expressions.

We now expose special parameters like Pageable and Sort to be used in SpEL expressions if they don't collide with existing named parameters.

Related pull request: spring-projects/spring-data-jpa#101
Related ticket: DATAJPA-564
DATACMNS-533 - Polishing of special parameter handling.

Collapsed variable gathering methods into one, make sure we expose all values (also null ones). Renamed unit test for ExtensionAwareEvaluationContextProvider according to the class name. Some further cleanups in the test case.

Related pull request: spring-projects/spring-data-jpa#101
Related ticket: DATAJPA-564
DATACMNS-533 - Added test cases for root object integration in SpEL extension API.

Changed SPI to expose a Function type rather than plain methods as well as an arbitrary root object.

Related pull request: spring-projects/spring-data-jpa#101
Related ticket: DATAJPA-564
DATACMNS-533 - Implemented handling of root objects.

Refactored the implementation of the dynamic lookup of properties and functions on EvaluationContextExtensions. All the reflective lookup logic has moved into an EvaluationContextExtensionAdapter.

We now also distinguish between the meta-information that can be looked up once and cached (so that we avoid reflection overhead for subsequent context creations).

Related pull request: spring-projects/spring-data-jpa#101
Related ticket: DATAJPA-564
DATACMNS-536 - Upgrade to Spring HATEOAS 0.15.0.RELEASE.
DATACMNS-527 - Updated changelog.
DATACMNS-536 - Updated changelog.
DATACMNS-536 - Prepare 1.9.0.M1 (Evans M1).
DATACMNS-536 - Release version 1.9.0.M1.
DATACMNS-536 - Prepare next development iteration.
DATACMNS-536 - After release cleanups.
DATACMNS-539 - DefaultCrudMethods now detects delete(T t) methods.

The CRUD method detection now also discovers delete methods taking the domain type as argument.

Related ticket: DATAREST-319.
DATACMNS-469 - Removed deprecations.
DATACMNS-538 - Updated section on pagination in reference documentation.

Reworked section that contained outdated parameter names and examples.

Original pull request: #91.
DATACMNS-543 - Avoid duplicate repository bean registration in XML namespace.

We're now firing the component registration event manually in RepositoryBeanDefinitionParser as ParserContext.registerBeanComponent(…) registers the given BeanComponentDefinition with the registry. As we do that manually before this previously resulted in the BeanDefinition overriding the very same one and container warnings in turn.
DATACMNS-544 - Indicate repository configuration has been active.

RepositoryConfigurationDelegate now registers the store-specific RepositoryConfigurationExtension as lazy-init BeanDefinition so that other parties can detect that definition.