572dc0ec14
* Short-circuit methods for lambdas from annotation When we have a `@ServiceActivator` or any other messaging annotations on `Function` or `Consumer` `@Bean`s, there is a restriction when we can't use lambdas because of target method argument type erasure in Java. * Use a `@Bean` method return to determine the target function argument type and wrap the call into the `LambdaMessageProcessor`. In this case we call the target method directly after possible payload conversion according expected generic type for `Function` or `Consumer`. There is just no reason to go a `MessagingMethodInvokerHelper` route for this lambda variants * Apply the short-circuit algorithm for Kotlin lambdas as well * Make some refactoring and improvements to `ClassUtils` if favor or similar API in the SF `ClassUtils` * Fix `No beanFactory` warning for the `ExpressionCommandMessageProcessor` * * Resolve Checkstyle violations * * Fix `resolveAttributeToBoolean()` argument name to be generic * Fix typo in the exception message for `IntegrationFlowDefinition.get()` * * Revert `ClassUtils.resolvePrimitiveType()` logic: an existing in SF does exactly opposite one
Spring Integration 
Checking out and Building
To check out the project and build from source, do the following:
git clone git://github.com/spring-projects/spring-integration.git
cd spring-integration
./gradlew build
NOTE: While Spring Integration runs with Java SE 6 or higher, a Java 8 compiler is required to build the project.
If you encounter out of memory errors during the build, increase available heap and permgen for Gradle:
GRADLE_OPTS='-XX:MaxPermSize=1024m -Xmx1024m'
To build and install jars into your local Maven cache:
./gradlew install
To build api Javadoc (results will be in build/api):
./gradlew api
To build reference documentation (results will be in build/reference):
./gradlew reference
To build complete distribution including -dist, -docs, and -schema zip files (results will be in build/distributions)
./gradlew dist
Using Eclipse
To generate Eclipse metadata (.classpath and .project files), do the following:
./gradlew eclipse
Once complete, you may then import the projects into Eclipse as usual:
File -> Import -> Existing projects into workspace
Browse to the 'spring-integration' root directory. All projects should import free of errors.
Using IntelliJ IDEA
To generate IDEA metadata (.iml and .ipr files), do the following:
./gradlew idea
Resources
For more information, please visit the Spring Integration website at: https://projects.spring.io/spring-integration