Support components-based development
A number of forum and uservoice conversations show that XLinks in their present implementation are not sufficient for common scenarios of component-based or modularized development. While XLinks may be an elegant and powerful idea, they are not a replacement functionality of working with subtrees provided by virtually every other system, from SVN to Git and including Plastic SCM 3. Further, a basic solution can be implemented in Plastic 4 with shell scripts and cloacked.conf. Some native means of working with components in subtrees of a repository would be very useful.
ima
shared this idea
We consider Xlinks a powerful enough solution for component oriented development in its current form, and most of the customers agree.
Git support is no better at all (it is quite weak compared) to Xlinks (you’ve to handle the dependencies manually with Git).