[ http://issues.apache.org/jira/browse/DERBY-1846?page=comments#action_12436608 ] Rick Hillegas commented on DERBY-1846: --------------------------------------
I'm afraid I don't understand the workaround. It appears that John regenerated all of the jars from scratch. If we're going to do that, then why are we writing this script in the first place? Why don't we just tell the users: 1) Unzip the source distribution. 2) Point ant.properties at your JDK 6 installation. 3) Build Derby. 4) Viola! > 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, modules.properties, 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
