The 3.2 series minimum requirement is java 1.5 but StatementCreatorUtils makes a call to Collections.newSetFromMap() which is since 1.6.
This is preventing us from upgrading from 3.2.5 to get the #15726 fix.
This issue manifests as java.lang.NoClassDefFoundError
P.S. we use animal sniffer to catch accidental usage of newer API methods in our builds, very handy.
#15937 spring-jdbc-3.2.6.RELEASE doesn't support JDK 5. ("duplicates")
The text was updated successfully, but these errors were encountered:
P.S.: We've been starting to use Animal Sniffer ourselves now, not least of it all due to this accidental breakage. Surprisingly we had hardly any breakages before, despite no specific tool support for detecting them.
Haha, websphere, no thankfully. I remember being stuck on java 1.3 for years after 1.5 came out because of websphere... Our deployment target is a shared tomcat 6 instance. Shared so it's a big effort to get all apps upgraded and tested at once, and not something i have any influence over unfortunately.
Have tested with 3.2.7-SNAP locally and my integration tests are passing again thanks. I'll have to stick with 3.2.5 until 3.2.7 is released though. Any ETA on that?