And as all prior versions of Java are EOL there's no reason not to be using Java 8.
And as all prior versions of Java are EOL there's no reason not to be using Java 8.
I also wonder what kind of data migration we'll be facing, since all of our persisted data is from Joda DateTimes, not Java 8 ones. Hopefully none.
That's not just for just dates or timestamps either. That's for data period.
It makes a whole lot of things that ought to be simple a lot harder.
I wish. When life (or rather a vendor) gives you java 6 libs which barely work on java 7, you make java7 lemonade.
The only thing I can see breaking would be reflection based invocations of new methods on existing interfaces (ex: Foo has a .bar() in Java 7 but not Java 6). You'd have to be doing something pretty unusual for that to bite you.
Oracle middleware libraries (to be fair, mostly acquired)...
I believe the problem was that in Java 8, something related to StringBuilder or string parsing was breaking hard. With Java7 it was ok, so we went with that.