[ http://issues.apache.org/jira/browse/DERBY-930?page=all ]
Kathey Marsden updated DERBY-930:
---------------------------------
Derby Info: [Existing Application Impact, Release Note Needed]
This change may impact existing applications as evidenced by the need to
change a related test in DERBY-1399. It requires at least a release note
documenting the impact. Once that has been done it will be easier understand
the scope of the problem and whether this is a regression that needs to be
addressed or a behaviour change accepted by the community.
DERBY-1399 has some informaition on this topic.
http://issues.apache.org/jira/browse/DERBY-1399?page=comments#action_12416359
Rick, could you add the release note to this issue? Bryan posted some helpful
Release Note format info at:
http://wiki.apache.org/db-derby/ReleaseNoteFormat?highlight=%28ReleaseNote%29
> 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
