[ http://issues.apache.org/jira/browse/DERBY-930?page=comments#action_12365670 ]
Andrew McIntyre commented on DERBY-930: --------------------------------------- Looks good, the getCodeSource method looks like it could be reused in sysinfo to take care of DERBY-668, among others, although I don't know if adding the getProtectionDomain permission would be a serious drawback. Dan could probably answer that question. Just a couple of minor cleanliness nits: Instead of creating a second section for jar helper targets, could you please move the new common targets to the section 'jar helper targets'? And why did you add dashes to the target names for the new common targets? It's ok, just out of convention with the rest of the target names in the main build.xml. I'll take a look at the problem when i have a moment and see if i can help. > 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 > Reporter: Rick Hillegas > Assignee: Rick Hillegas > Attachments: bug930.diff, bug930_problem.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
