[ http://issues.apache.org/jira/browse/DERBY-1547?page=comments#action_12427927 ] Deepa Remesh commented on DERBY-1547: -------------------------------------
Hi Narayanan, The failures in the above tests do not look related to your patch. These set of tests explicitly check the version and are expected to get modified when a new release is created. They are listed in "regex.masters" target in tools/release/build.xml. I think there was a problem in the execution of this target (which is already fixed) when the new branch was created. The above tests are now passing. We should not add sed files to sed out the version checks for the above tests. I do not know if this information is documented anywhere. Anyone else know? For upgrade test failure, I have created DERBY-1689. Thanks, Deepa > Add svn version number to DatabaseMetaData getDatabaseProductVersion and > getDriverVersion() to improve supportability > ----------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1547 > URL: http://issues.apache.org/jira/browse/DERBY-1547 > Project: Derby > Issue Type: Improvement > Components: JDBC > Affects Versions: 10.1.3.2 > Reporter: Kathey Marsden > Assigned To: V.Narayanan > Priority: Minor > Fix For: 10.2.0.0 > > Attachments: DERBY-1547_v1.diff, DERBY-1547_v1.stat > > > getDatabaseProductVersion and getDriverVersion() report only the four digit > Derby version number and not the svn build number. It would be useful to > return the full version including the build number as sysinfo does: e.g. > "10.1.2.4 - (392472)", That way it will be clear from application logs that > collect this information exactly what revision level they are running if they > are using rolled up fixes on the maintenance branch between releases. > There may be risk in doing this however if applications are parsing the > version information, but hopefully they will use getDatabaseMajorVersion() , > getDatbaseMinorVersion, getDriverMajorVersion, and getDriverMinorVersion for > such proccessing. -- 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
