[ http://issues.apache.org/jira/browse/DERBY-930?page=comments#action_12416591 ]
Rick Hillegas commented on DERBY-930: ------------------------------------- I think that derby-dev should continue to discuss the issue which Olav has analyzed in DERBY-1399. I will continue this discussion shortly. Based on that discussion, we can decide what to put in a release note. It's unclear to me how to divide JDBC4 functionality among release notes. This issue may deserve a release not by itself, or it may be a subcase of some larger release note for JDBC4 features. But in any event, I agree we should attach some description to this issue for rollup somewhere in the 10.2 release notes. In addition, this behavior should be documented in the user guides. The analysis of user guide changes can be found in DERBY-1271. > Add support for autoloading of Derby client drivers > --------------------------------------------------- > > Key: DERBY-930 > URL: http://issues.apache.org/jira/browse/DERBY-930 > Project: Derby > Type: New Feature > Components: Build tools, JDBC > Reporter: Rick Hillegas > Assignee: Rick Hillegas > Fix For: 10.2.0.0 > Attachments: ClassloadingTest.jar, bug930.diff, bug930_problem.diff, > bug930_problem2.diff, bug930_rev2.diff, bug930_rev3.diff > > Write Derby's driver names into the correct spot in derby.jar and > derbyclient.jar so that the 1.6 vm autoloads Derby drivers. Section 10.2.1 of > the JDBC4 spec describes the details. -- 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
