Description Andrew Cattle 2008-12-16 11:10:07 EST

I remember discussing this in a p2 call but I can't seem to find where the discussion has been captured in the minutes. I'm logging this bug before it is forgotten.

Currently, composite repositories lazily load their children. However, it is my understanding that part of the contract with UI is that a repository must be finished loading before it can be displayed for efficiency reasons. However, I'm worried that loading all children at the composite's load time and storing them as IRepostiory objects might have a greater chance of leading to synchronization issues than loading them right before use as this would move them outside of the RepositoryManager.

This results in two questions:
1) What does it mean for a composite repo to be loaded? Just the repo or the repo + children?
2) How should composite repos handle the failed loading of a child?

Currently we log the failure and just continue with the next repo. While this increases robustness, it leaves us int he situation where the same repository, without changing it's own content, which have different results each time a method such as "getArtifactKeys()" is called depending on what children are loaded. Perhaps we create a property which says whether or not we care?