[ http://issues.apache.org/jira/browse/DERBY-513?page=comments#action_12433081 ] John H. Embretsen commented on DERBY-513: -----------------------------------------
There is actually a patch available for this issue, but it is more than one year old, so when I tried applying it to the current trunk, it was rejected. But it's a simple patch, so once it is generated from a newer working copy, it will most likely apply cleanly... So I'm not setting the 'Patch Available' flag, but it would be good to get this out of the way soon... :) > Add information on how to change the jdk version a test will be compiled with > in testing/readme.htm. > ---------------------------------------------------------------------------------------------------- > > Key: DERBY-513 > URL: http://issues.apache.org/jira/browse/DERBY-513 > Project: Derby > Issue Type: Improvement > Components: Documentation > Reporter: Fernanda Pizzorno > Assigned To: Fernanda Pizzorno > Priority: Minor > Attachments: DERBY-513.diff > > > Add the following item to section 4.7 Adding a new test: > * If the test file must be compiled using jdk1.4 instead of jdk1.3, > * edit the build.xml file located in the same directory as the test > * exclude the new test file under compilet1 > <exclude name="${this.dir}/newfunctest.java"/> > * include it under compilet2. > <include name="${this.dir}/newfunctest.java"/>. -- 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
