Hudson subversion checkout causes files to appear modified if they have no
revision history

I found this issue when experimenting with the Hudson Maven Release Plugin. mvn
release:prepare would always fail indicating that changes were detected in the
working copy of the source. This should never happen since "Use update" is
unchecked for the project - a clean copy should be checked out. Verified this
by disabling "Source Code Management" for the project and using "M2 Extra Steps
Plugin" to execute a command line checkout of the code before the build. No
differences detected after this (but other problems using release plugin as a
side effect of the command line checkout - so not a good workaround).

When investigating, I determined that this was happening with all of my Hudson
builds, but I only detected it due to the maven release failing.

It appears that something is awry during change log generation after checkout if
a file has no revision history but contains an "$Id:$" keyword expansion.
Command line svn status will report there are local changes to any file that is
a new file with no revision history (newly checked in files) if run in the
Hudson workspace for that project.

A svn diff on one of the files results in the following - notice the discrepancy
of the keyword expansion "$Id:$":

Index: RSAFileEncryptionUtil.java
===================================================================
— RSAFileEncryptionUtil.java (revision 162)
+++ RSAFileEncryptionUtil.java (working copy)
@@ -31,7 +31,7 @@

• A tool for securely reading and writing file content using RSA wrapped AES
  encryption
  *
• @author BMS

• * @version File/Rev/Date/Author of last commit: $Id:$
  + * @version File/Rev/Date/Author of last commit: $Id$
  */
  @SuppressWarnings( {"OverloadedMethodsWithSameNumberOfParameters"}

  )
  public class RSAFileEncryptionUtil