Hi all,
As per my previous post I'm in the process of implementing an extended
AccuRev
provider.
AccuRev, apparently like Perforce and Clearcase, keeps track of user
checkouts
in "workspaces". These workspaces are uniquely named across the repository,
and
the physical filesystem locations are not permitted to overlap.
Consequently the release plugin's checkout to the target/checkout
sub-directory
is problematic. It looks like the "isPersistCheckout()" method from SCM-113
is
intended to resolve this very issue, but I have a few questions on that.
1) Why is the default "false".
- It appears that the previous behaviour was more equivalent to "true".
- The tck-tests (eg the checkin/tag tck tests) assume by their behaviour
that
the default is "true".
- The only downstream use that sets "false" is the release plugin.
Everything
else sets it explicitly to "true" (of course I can't search for things
that
don't set it explicitly, so there might be others)
2) What is the difference between isPersistCheckout == false, and the
"export"
command?
- Both seem to extract a set of files to a directory, without the
intention of
updating or committing back.
- It feels strange that downstream users have to set a flag in the
provider
repository which is otherwise "owned" by the provider.
Thanks,
Grant.
