[ http://issues.apache.org/jira/browse/DERBY-1380?page=comments#action_12415037 ]
Rick Hillegas commented on DERBY-1380: -------------------------------------- The code looks solid. This makes it possible to once again connect to databases when running with build 86 or higher of the 1.6 jdk. The unsatisfied signatures do not affect existing applications and can be cleaned up in later submissions. The derbyall failures you are seeing are the familiar ones we already see under 1.6--plus the extra complaints about unsatisfied signatures. Committed at subversion revision 412204. As of this submission, you must use build 86 or higher of jdk1.6 in order to build and run Derby with JDBC4 support. > Interface changes introduced in Mustang build 86 > ------------------------------------------------ > > Key: DERBY-1380 > URL: http://issues.apache.org/jira/browse/DERBY-1380 > Project: Derby > Type: Bug > Components: JDBC > Versions: 10.2.0.0 > Environment: Any > Reporter: Dyre Tjeldvoll > Assignee: Dyre Tjeldvoll > Priority: Critical > Fix For: 10.2.0.0 > Attachments: derby-1380.v1.diff, derby-1380.v1.stat, derbyall_fail.v1.txt > > Build 86 of Mustang introduced changes to the Connection interface that were > not compatible with the existing Derby implementions. > createArray() was renamed createArrayOf() and setClientInfoProperties() now > throws SQLClientInfoException (rather than ClientInfoException). The result > of this is that it is not possible to build Derby with build 86. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
