Spring Boot now doesn't allow by default to override beans in the
application context
* Add `spring.main.allow-bean-definition-overriding=true` to the
test class definition to reflect the purpose of the downstream
configurations
* Fix TCP tests to use OS-selected port
https://build.spring.io/browse/INTSAMPLES-NIGHTLY-2413
Modify all the `tcpclientserver` tests to rely on the OS-selected port,
in other words set `0` to the server port and get the real port for the
client when server is listening
* * Upgrade to Gradle-4.6
* Fix Travis config do not perform assemble task
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-2342
The `TcpClientServerDemoTest.testMultiPlex()` relies on the
`HashSet.size()` for assertion meanwhile that property is not `volatile`.
Since we change the state of the `HashSet` from other threads
the non-`volatile` property is not reliable source of information.
* Change the test-case to use `LinkedBlockingQueue` instead of `HashSet`
which uses `AtomicInteger` to track its `size`
https://build.spring.io/browse/INTSAMPLES-NIGHTLY-2256
The `AggregatorDemoTest` fails sporadically with no second part from
reply.
That might be as a result of the cached consumers in the
`CachingConnectionFactory`, so several `<int-jms:inbound-gateway>`
for the topic using the same connectionFactory essentially end up
using the same consumer sequentially.
And Broker considers them as a single consumer, therefore only one
message is sent.
https://build.spring.io/browse/INTSAMPLES-NIGHTLY-2239/
Having Hibernate and EclipseLink in the same application isn't a goal.
On the other hand the sample must be concentrate on the Spring Integration,
not a complexity brought by the Spring Boot auto-configuration override.
* Remove the EclipseLink support from the JPA samples and rely only on
the Hibernate auto-configuration
* Remove an appropriate message from the README
https://build.spring.io/browse/INTSAMPLES-NIGHTLY-2211
It isn't clear why second message copy is lost, so increase timeout
in case of some fluctuations in the ActiveMQ.
Also increase logging level to DEBUG to see some info in the next failure
The `Jackson2JsonObjectMapper` tries to load any available modules for
the Jackson `ObjectMapper` via `findAndRegisterModules()`.
But if we have a module but don't have a target library, we end up with
the `ClassNotFoundException`.
In our case we fail with the Kotlin because Spring Boot provides
`com.fasterxml.jackson.module:jackson-module-kotlin` dependency and
leaves the rest of required libs for the target application.
* Exclude `com.fasterxml.jackson.module:jackson-module-kotlin`
from all the dependencies.
* Spring Integration `Jackson2JsonObjectMapper` should be revised to use
`Jackson2ObjectMapperBuilder` - https://jira.spring.io/browse/INT-4318
