On 20 Mar 2009, at 23:16, Adrian Cole wrote:

Hi, devs.

As you may know, JDK 5 is officially end of life this October. As that time is not too far away, I thought we could consider how we want to address the issue.

As I see it, we have a few choices:

1. set default binary to JDK 6 and produce a separate mvn artifact with classifier jdk15 for compatibility.
2. set default binary to JDK 5 and produce a separate mvn artifact with classifier jdk6 for compatibility.
3. do nothing and only produce a JDK 5 jar.

I reckon #3. We're not doing anything JDK6-specific in the code base so no real need for 1 & 2.