| Q: How do I avoid circular references and get the job done [message #575496] |
Fri, 26 January 2007 22:34 |
 Rob Robason
Messages: 72
Registered: July 2009 |
Member |
|
|
After experiencing the cons of creating circular references, I'm eager to
avoid that in the future, but some of the plugins I'm working on seem to
demand them. I'm looking for a way to structure my information to avoid
catastrophe.
I've opted to use Option 1: Organizing the content packages along the major
areas of concern of the plug-in. from the Packaging Guidelines in the
Plug-in Development Guide. My plugins are structured along the lines of the
CMMI process areas.
What I'm finding now is that dependencies between process areas are forcing
me to move more and more content into my top level plugin in order to avoid
circular references.
So here's my dilemma: I'd prefer to create a single plugin with multiple,
per-process-area, content packages that can cross reference each other, but
I need to have multiple people working on these materials in parallel, and
collisions in the plugin.xmi file seem to preclude that approach.
Am I missing something? Is there a way around this?
--
Rob Robason
Software Process Manager
Wind River Systems
|
|
|
Powered by
FUDForum. Page generated in 0.04370 seconds
] 
Search
Help
Register
Login
Home
