On 2015/04/06 22:16, Mikhail T. wrote: > On 04/06/15 16:00, Matthew Seaman wrote: >> That might be possible, but it would result in dropping a serious >> slice of functionality from the connector. > Which functionality is it? If an old compiler is truly required at > all, it can only be to generate code to run in an old JVM. > > Since FreeBSD stopped offering java-1.5 long ago, this can not > possibly be a concern... And, of course, even a modern javac can be > asked to generate 1.5-compatible byte code. > > None of these changes would be particularly /pleasant/ -- I, > personally, am always revolted by the innards of a pom.xml or > build.xml -- but they ought to be /possible/...
build.xml says this: Compiling Connector/J ===================== Connector/J 5.1 supports both JDBC3 and JDBC4+ with a single code base. This requires JDBC3 classes to be compiled with Java 5 and JDBC4+ to be compiled with Java 6. The variables 'com.mysql.jdbc.jdk5' and 'com.mysql.jdbc.jdk6' are used to find the respective compilers when building the driver. Side by side with these, the variable 'com.mysql.jdbc.extra.libs' must point to the location of third-party libraries that we don't distribute and are required for compiling. Further details can be found in http://dev.mysql.com/doc/connector-j/en/connector-j-installing-source.html. So anyone using JDBC3 would be disappointed by our chopping it out. I have precisely zero idea how many people that might be, or indeed how much call there is for JDBC3 adaptors in general. Cheers, Matthew
signature.asc
Description: OpenPGP digital signature
