https://build.spring.io/browse/INTSAMPLES-NIGHTLY-2398/
* Remove `FileExistsMode.APPEND_NO_FLUSH` from the app.
It's not reliable for unit testing: keeps resources opened and cause
false positive assertions but at the same time no any interactions with
mock `session`
* Clean up test directories before and after tests
https://build.spring.io/browse/INTSAMPLES-NIGHTLY-JOB1-2397
To avoid race conditions with the test data and auto-started channel
adapter, it would be better to have channel adapter not started in the
beginning and prepare test data and only after that start it manually.
The race condition is when we have old data in the directory to poll
https://build.spring.io/browse/INTSAMPLES-NIGHTLY-2059/
Fix `JmsMockTests` stubbing via making endpoint stopped before mocking
Force SI and SF versions via their BOMs imports
Regenerate POMs including `dependencyManagement` for BOMs customization
Remove `@IntegrationComponentScan` from Boot samples
Since the latest Spring Boot utilize already `@IntegrationComponentScan` for the `@SpringBootApplication` class package, there is no reason to worry about lost `@MessagingGateway`
Reflect Kafka samples changes according latest Spring Boot fixes
* Fix compatibility after Java DSL migration to the SI Core
* Also upgrade all the JMS sample to the JMS 2.0
* Fix default `connectionFactory` bean reference to the current `jmsConnectionFactory`
* Remove unsupported JPA-1.0 Spec via `OpenJpaAutoConfiguration`, since the minimum now is JPA-2.0
* Remove non-lambda sample since minimum now is Java 8
* Rename `PromiseTest` to `MonoTest` and fix it to Reactor 3.0
* Fix `stomp-server.xml` to use proper Reactor 3.0 `eactor.util.function.Tuples` for SpEL
* Regenerate POMs
https://build.spring.io/browse/INTSAMPLES-NIGHTLY-1898/
There is no guarantee that if `File.exists()`, the real write to file has occurred
* Add `while()` to check not only `File.exists()` but also its `length()` only after that proceed to assert logic
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
Fixes GH-180 (https://github.com/spring-projects/spring-integration-samples/issues/180)
* Apply `PollerSpec.errorChannel(String)` style
* Replace `fileNameExpression()` to `fileNameGenerator()` to avoid `No BeanFactory` for `EvaluationContext`
* Use `.trigger()` instead of `.handle()` for `FileWritingMessageHandler.trigger()`
* Fix race condition in test, when file exists already, but there is no content yet
JIRA: https://jira.spring.io/browse/INTSAMPLES-149
Polishing - PR Comments
Polishing - Work Around DSL Issue #119
Make test compatible with Windows.
Also reset Application context `DirtiesContext.ClassMode.AFTER_EACH_TEST_METHOD`.
Since tests uses the same target resources we should be sure that they use clear foundation before running
