Community
Participate
Working Groups
I have an Update Site project that contains a PSF file that describes the set of projects needed to build the update site. As team members around the world add new projects to the update site, other members update their local copy of PSF to import projects into their local workspaces. It would be nice if we could right-click on the PSF file and "Import Missing Projects". This action would go through the current workspace and determine which projects are already present, then import those that are missing. The action should examine the CVS files of any existing project (including projects that are closed) to determine if existing copies are from the same repository and provide an option to replace existing projects if the repository location has changed. I'm not an expert in Team issues, so there may be other factors to consider as well.
BTW, the functionality is almost available today. The "Import Project Set" menu does warn that projects already exist and offers an option to replace or skip, but this occurs one project at a time. What I'm suggesting is a slight optimization that would essentially request that only new projects (or projects that have moved) be considered.
I think that this is covered by bug 155407 (i.e. if we had the prompt that showed all projects and those that already existed, we won't need a separate action). *** This bug has been marked as a duplicate of 155407 ***