continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ArneD <>
Subject Re: Update over scm-local does not delete files removed from source dir
Date Wed, 13 Sep 2006 16:28:48 GMT

Emmanuel Venisse wrote:
> Are you sure it isn't possible to checkout sources in a specific folder
> with cleartool?

It is possible with snapshot views. My ClearCase know-how is limited, but I
am quite sure it is not possible with dynamic views.

Do you think the suggested enhancement for scm-local would be useful and
make sense? Not only in combination with ClearCase dynamic views but for
other usage as well, e.g. testing.


>> That's true. Maybe we could enhance scm-local to keep its own metadata?
>> In
>> particular, 
>> scm-local could maintain a simple file, say .maven-scm-local, that
>> contains
>> as plain text the list of files in the source directory, as seen during
>> the
>> last checkout or update operation:
>> - During checkout, the file .maven-scm-local is created in the checkout
>> base
>> directory. Its just a plain text file containing the list of files that
>> have
>> been checked out.
>> - The update command looks for the file. If it is there, it compares the
>> contents of that file to the current source directory contents (including
>> subdirs). All files that are in .maven-scm-local but are no longer in the
>> source dir, have been deleted in the source dir. The update command
>> therefore removes them from the checkout dir.
>> - If for whatever reason .maven-scm-local is not there, the update
>> command
>> won't delete any files. That way, we're backwards compatible.
>> - After completing the update process, the update command rewrites the
>> .maven-scm-local metadata file.
>> - Even the changelog command can interpret .maven-scm-local
>> - For add and checkin commands, I don't think that changes are needed.
>> What do you think?
>> Regards,
>> Arne

View this message in context:
Sent from the Continuum - Users forum at

View raw message