For whatever reason, subversion does not do keyword expansion by default. That means that even if you litter your sources with $Id: datafaberdb.sql 352 2007-12-12 20:42:13Z seba $, $Author: seba $, etc, they will stay as is. So, even before you begin working with a subversion repository, make the following changes to your subversion client configuration file:
The setting in the config file won't do anything if you have already a working copy of a repository and you don't have keyword expansion enabled on every file... So you'll need to explicitly tell Subversion to expand keyword, and this can be done with the command line svn program as follows:
### Section for configuring miscelleneous Subversion options. [miscellany] enable-auto-props = yes ### Section for configuring automatic properties. [auto-props] *.sql = svn:keywords="Author Revision Id" *.java = svn:keywords="Author Revision Id" *.jsp = svn:keywords="Author Revision Id" *.xml = svn:keywords="Author Revision Id"Of course you may add as many file types as you want and as many keywords as supported by subversion. However, this setting should be done on every developer's workstation (I could not find a way to enforce it at the repository level, I'd like to be corrected if I'm wrong).
The setting in the config file won't do anything if you have already a working copy of a repository and you don't have keyword expansion enabled on every file... So you'll need to explicitly tell Subversion to expand keyword, and this can be done with the command line svn program as follows:
svn propset --recursive svn:keywords "Id Author Revision" webapps/*assuming that webapps is a directory under the current directory where you have some files that need keyword expansion enabled. You need to commit this change to the repository, or nobody will see the expanded keyword, so:
svn commit -m "adding keyword expansion to existing files"Finally, you can update your working copy to see the expanded keyword.