- add testcase (which used to cause compiler failure)
- remove <?> from PayloadMatcher to fix error
- add casts to FileInboundCAWRDTests to deal with backwards compatibility breakage
In some cases backwards compatibility is broken, see INT-1790 for details.
Synchronize with changes in buildSrc that add repositories
declared in gradle script(s) to generated maven poms during
`generatePom` task.
Issue: GRADLE-48
For ease of use by those (a) more familiar with Maven or (b) relying
on m2eclipse support within Eclipse/STS, generated poms are now checked
in. Changes to these files will be overwritted on subsequent gradle
builds.
Any changes to project dependencies should first be reflected in
build.gradle; then run `gradle generatePom` or simply `gradle build`
to see the change reflected in the pom(s).
Note that org.springframework.integration.ip.tcp.TcpInboundGatewayTests
currently fails when running `mvn clean test` from the root. This
problem does not manifest when running `gradle clean test`. The latter
is what's most important; Gary has been contacted to take a look at the
former.
Issues resolved:
INT-1609, INT-1610, INT-1611
buildSrc updated to use latest Gradle wrapper. See buildSrc git log
for complete details; in short, eclipse JDT prefs are now auto-generated
and the gradle daemon is no longer 'on by default', but must be enabled
with --daemon or -Dorg.gradle.daemon=true.
* removed all existing jdt preferences files in favor of auto-generation.
* removed .springBeans from .gitignore; this file should be
source-controlled for consistency and convenience.
* removed illegal @Override annotations. Eclipse/STS now catch these
properly!
POMs removed in favor of Gradle build. pom.xml added to .gitignore
to accommodate future generation of source-level poms for those who
wish to use m2eclipse tooling in STS (to come in a later commit)
