(Posting to users list, since this is more a user-oriented issue.)
I think it’s time we drop Java 5 support in JRuby.
Five years ago we took the then-controversial step of dropping Java
1.4 support, largely so we could take advantage of generics and
annotations throughout the codebase. These days, Java 5 is over six
years old, and I think it’s time we took the next step.
Other than Java 5’s age, there’s plenty of reasons to do this:
Linux distributions often don’t even have packages for Java 5, since
it was never an OSS codebase.
It is no longer possible to get Java 5 for OS X (Snow Leopard and
higher simply don’t have Java 5 builds available anywhere).
The lack of Java 5 support on the JRuby team’s dev systems makes it
increasingly difficult to avoid using Java 6+ features. I just did it
again last week (String.getBytes(Charset)).
Android is actually based on Apache Harmony SE 6 (not 5 as I was led
to believe) so it doesn’t represent a Java 5 hold-out.
Java 5 has been EOL by Sun/Oracle for over two years, which means no
further fixes, patches or development have gone into it since that
Java 5 versions for most exotic platforms are now old, EOL, and
buggy as hell (IBM J9, HP/UX, OpenVMS, …)
So I guess I’m asking for a good reason why JRuby 1.7 shouldn’t drop
Java 5 support, finally, and only support Java 6+. Anyone? Anyone?