Since we provide a custom `FileNameGenerator` via `fileNameExpression` we should ensure somehow `BeanFactory` injection to that
`FileWritingMessageHandlerSpec` is a `FactoryBean` since version DSL `1.2` and a particular `BPP` takes care about `Spec` internals and register custom `FileNameGenerator` as a bean.
Use standard `FactoryBean` injection in the `lines()` flow to populate the target `FileWritingMessageHandler` to the flow
Generate pom for all project to apply SI Java DSL 1.2 GA
Make `PromiseTest` more fast decreasing `sleep()` in the `MathService`
Kafka-0.10.0 Compatibility
Upgrade to Spring Boot 1.4.0.RELEASE
Regenerate poms according to upgrades
When just importing the ftp example as a maven project, I ran into the issue of a slf4j version discrepancy described here:
http://www.slf4j.org/faq.html#IllegalAccessError
This is solved by adding the specific version dependency of `slf4j-api`.
* Add the specific `slf4j-api` dependency to the Gradle script
* Change the dependency scope for `slf4j-` impl to the `runtime`.
* Regenerate POMs
JIRA: https://jira.spring.io/browse/INTSAMPLES-137
* Upgrade to Boot 1.1.7
* Fix several Boot apps to get deal with `args`, e.g. `--debug` option can be useful for Boot
* Provide a loca copy for JavaScript files (`sock.js` and `stomp.js`) to avoid extra Internet connection on testing
INTS-137-2: Make JavaScript cross-browser
Some additional polishing to the server config, like `logging-channel-adapter` for server message flow
JIRA: https://jira.spring.io/browse/INTSAMPLES-130
Enable `Run As | Run on Server ...` when using eclipse.
The wtp config was lost when the samples were converted
to gradle.
Upgrade to SI-4.0.2 and Boot 1.1.0.RELEASE
Polishing according upgrading
