Okay, first I'll admit that I do understand what the point is supposed to be and so the title is more rhetorical than anything. I can't seem to figure out how to organize documentum projects in composer so that it does not require me to install my SBOs to every content server. If I create a project that contains a TBO and that TBO requires the use of an SBO then I must reference the project that contains the SBO and in doing so commit to installing both projects into every content repository that needs the application. I'm looking for alternative methods for providng the SBO code but I have not discovered any yet but I'm accepting suggestions?
My goal is the following:
One project for artifacts common to every content server (default alias set, base custom types, etc)
One project for the global repository that basically just contains SBOs and not much else.
One project for each different content repository application (not including the global repository itself)
If I can achieve this configuration then my development deploy process would be the following:
1. deploy common artifacts to all repositories (only requires updating occasionally when something major changes)
2. deploy SBOs to global repository only
3. deploy custom application that are targeted to specific content servers but only include aspects, overridden base types, TBOs, lifecycles, overriden alias sets, etc, no SBOs and nothing common to all content servers. My projects should be basically scoped to an entire content repository and there is rarely (if ever) more than one project per repository not including common artifacts.
Any ideas?
