I would love to see a 1.5 deprecation warning to expedite the migration to Java 6 as the oldest support. One of the only "breaking" API changes between Java 5 and Java 6 is JDBC 4.0 -- and that only affected things that attempted to wrap JDBC, such as for extended logging.
There are probably some people stuck on Java 5, but likely the same ratio as were stuck on Java 1.3 in the past. -Spencer >________________________________ > From: Daz DeBoer <darrell.deb...@gradleware.com> >To: dev@gradle.codehaus.org >Sent: Friday, October 18, 2013 6:34 AM >Subject: [gradle-dev] Deprecate Java 1.5 support? > > > >G'day >HttpClient is one of the many libraries that we depend on that will soon be >removing support for Java 1.5. I'm thinking it might be a good idea to >deprecate support for Java 1.5 in Gradle prior to releasing Gradle 2.0. > > >That way, while we won't _need_ to remove Java 1.5 support immediately with >Gradle 2.0, neither will we need to wait until Gradle 3.0. Deprecation would >send a message, and hopefully we'd hear from the community how widespread the >usage is. > > >Thoughts? >Daz > >
