e6225926c4
* Register `BeanDefinition`s for DSL components. That way we get a gain when the `BeanDefinition` is involved, e.g. Spring Cloud Function uses this approach to determine the generics of the target `Function` class * This programmatic `BeanDefinition` registration approach (available since SF-5.0) allows us to avoid some manual lifecycle processes: bean initialization, autowiring, event listener registration etc. * Rework `IntegrationFlowContext` to register and remove `BeanDefinition`s as well * Remove unused `registerComponents` flag from the `StandardIntegrationFlow`. With the proper logic in the `IntegrationFlowContext` it does not make sense any more * Remove redundant `AnnotationGatewayProxyFactoryBean` in the `IntegrationFlows`; populate `defaultRequestChannel` directly to the `GatewayProxyFactoryBean` instance * Add an overloaded `IntegrationFlows.from(Class, String)` to allow to specify an explicit bean name for the target gateway proxy * Extract and populate bean name from the `@MessagingGateway.name()` in the `AnnotationGatewayProxyFactoryBean` * Stop lifecycles in the `AmqpTests` after using for proper test suit shutdown
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: http://projects.spring.io/spring-integration