Yes. You're in the way.
The main use of this feature is usefull when you have common code (libraries, for example) in a repository, and you want to use it to develop other projects.
I will explain this with a example: We have two repositories:
commonLibrary and
project1.
The first step is creating a controlled folder in project1 (for example called
lib), where you will mount all content of
commonLibrary repository.
Then, you must specify the following selector:
Code:repository "commonLibrary" mount "/lib"
path "/"
branch "/main"
checkout "/main"
rep "project1"
path "/"
branch "/main"
checkout "/main"
When you do a update on your workspace, all content of project1 will be downloaded, and also, all content of commonLibrary will be downloaded under folder 'lib'
Now you can use Plastic SCM in a standard way.
Regards,
Daniel
