I have to maintain a set of projects working from multiple machines using multiple branches from source control repositories, plus the addition of virtual machines for automated testing. The current problem with the CCS v4 Eclipse workspace paradigm is that it only supports natively absolute pathing for the workspace. This means in my current development setup, I need to maintain 6+ workspaces making sure that when I make a change in one workspace I have to replicate that change to all the other workspaces.
This problem could be alleviated with the support of a portable workspace option in CCS v4 by replacing the absolute pathing with relative pathing. This would allow me to run my workspace from any directory structure on any machine I need to work from and be able to store the whole thing in my SCM system.
Is there any technical reason why relative pathing and portable workspaces are not supported in CCS v4? Yes, I do know individual projects within the workspace can be made portable, but that does not remove the hassle of maintaining multiple workspaces across machines and enviroments on a single project set that need the same workspace settings.
