Luciano Resende wrote:
If Mark is willing to check the missing files, +1 for the updates. I
do find this useful from time to time.

I also agree that developers should configure their IDE and SVN to
proper add the tags and any necessary SVN properties to make this
work.

On Thu, Mar 27, 2008 at 9:44 PM, Vamsavardhana Reddy
<[EMAIL PROTECTED]> wrote:
+0.5

 These numbers are expected to help in quickly getting to the revision in
 which these files are modified.  So, if the last revision on the file just
 added this header, it is not of much use.  I would suggest that instead of
 making a change to just add these headers, we add these headers in the new
 files and any existing files as we add/modify files.  This is a practice I
 follow for my Geronimo commits.

 Also, the committer's machine should have the the subversion client
 properties set appropriately so that these svn:keywords get added to the
 newly created files.  These settings help in avoiding explicitly adding the
 svn:keywords on newly created files.  See [1].

 [1] http://cwiki.apache.org/GMOxDEV/subversion-client-configuration.html

 ++Vamsi



 On Fri, Mar 28, 2008 at 2:25 AM, Mark Combellack <[EMAIL PROTECTED]>
 wrote:



 > Hi,
 >
 > I've been looking through the Tuscany source code and noticed that some
 > files have a @version containing the SVN revision number in their JavaDoc
 > headers but others do not.
 >
 > As an example, @version might look like:
 >
 > /**
 >  * Some JavaDoc for the class
 >  *
 >  * @version $Rev: 598005 $ $Date: 2007-11-25 16:36:27 +0000 (Sun, 25 Nov
 > 2007) $
 >  */
 >
 > I would like to go through the Tuscany source code and add this header
 > where
 > it is missing. This would involve a large number of minor changes to the
 > Tuscany tree so I wanted to run it by everyone to make sure no-one had a
 > problem with me doing this at this time.
 >
 > I'll probably start this next week unless there is an objection.
 >
 > Thanks,
 >
 > Mark
 >
 >
 >
 > ---------------------------------------------------------------------
 > To unsubscribe, e-mail: [EMAIL PROTECTED]
 > For additional commands, e-mail: [EMAIL PROTECTED]
 >
 >




I haven't used this information yet, probably because it's not
always reliably available.  If we were all maintaining it with
our checkins, I think I would find it useful.  I am happy to
get myself set up correctly to add it to files that I create.

  Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to