Olaf Kober Posted October 6, 2017 Report Share Posted October 6, 2017 Our current workspace setup contains a xlink to another repository. The xlinked folder contains build scripts and build tools. Now, when switching between different branches, it is often the case that these branches refer to different versions of the xlinked repository. The current behavior of Plastic SCM client (5.x and 6.x) is that it DOES NOT update the xlinked folder automatically. We have to manually update the workspace once to get the correct files in the xlinked folder. If one forgets to do the update, it sees the up-to-date files of the repository, but non-matching build tools/scripts in the xlinked folder. That behavior is confusing for most users, especially new ones. Is there a configuration option for changing this behavior? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.