Use checksums for testing files for changes.

Today RDi uses timestamps for testing local and remote members for changes. If the timestamps do not match, the Remote Reconciler assumes that a member was changed on the local or remote system. But of course that may not be true. For example, members are always considered to be changed, if an i Project is copied from an old workspace to a new workspace, e.g. if:

• a workspace was broken

• a new version of RDi shall be tested

• an i Project has been checked out to a new workspace

In these cases the developer first needs to start the Remote Reconciler and then check each member for changes if the compile library is shared with other developers. Even a dedicated compile library of his own would not help, because all members are "incorrectly" reported as "Changed".

Please change the way of testing members for changes and use a checksum in addition to timestamps. First compare the checksums. If the checksums match the members are equal and can be considered as unchanged. If the checksums are different, check the timestamps to figure out the new version.

The checksum of a member could be stored along with the timestamp in the *.properties file of the member. This way it would be uploaded to a Git or SVN repository along with the member. Cloning the repository to a new workspace would not mark all members as changed and the developer could start working immediately without comparing each member by hand.