[ http://issues.apache.org/jira/browse/DERBY-1547?page=comments#action_12429478 ] Andrew McIntyre commented on DERBY-1547: ----------------------------------------
"The above solution has been based on the suggestions received for this issue in using a property file as the point where the version information will be stored so that we no more need to update multiple master files when bumping version information but only replace one property file." We already have one properties file that contains the version number: tools/ant/properties/release.properties. We should not have another that needs updating when changing the version. I suggest that you generate your properties file from that file at build time. If the goal for this issue is now to completely remove the need to update master files when bumping the version, then the metadata tests that call getMajor/MinorVersion() and only output that part of the version would also need to be accounted for. That seems outside of the scope of this issue's description, though. > 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.1.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
