[ http://issues.apache.org/jira/browse/DERBY-1846?page=comments#action_12436059 ] Andrew McIntyre commented on DERBY-1846: ----------------------------------------
org/apache/derby/modules.properties in derby.jar needs to be updated to include the information about the JDBC 4 driver. It sounds like something went wrong with the update. That should be handled by the part of the script starting with "# patch up modules.properties so the driver will load" The update is very simple: unpack modules.properties from derby.jar, then cat the needed updates to the end, trimming the line endings as necessary. It then is picked up with the rest of the classes when derby.jar is updated. Can you check and see what happened to modules.properties during the update? > Create a script that allows users to easily update their Derby jars with the > JDBC4 classes. > ------------------------------------------------------------------------------------------- > > Key: DERBY-1846 > URL: http://issues.apache.org/jira/browse/DERBY-1846 > Project: Derby > Issue Type: Improvement > Components: Demos/Scripts > Affects Versions: 10.2.1.0 > Reporter: Andrew McIntyre > Assigned To: Andrew McIntyre > Fix For: 10.2.1.0 > > Attachments: derby-1846-v1.diff, derby-1846-v2.diff, > derby1846-batchFix_v1.diff, output_batchFix_v1.txt > > > Since the resolution of the JDBC 4 licensing issue was to not ship a build > that includes Derby's JDBC 4 code, but continue to ship the Derby source > files for them, a script which automatically compiles and updates the Derby > jars with the JDBC 4 classes would be useful. -- 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
