Community
Participate
Working Groups
"Import Existing Project" action allows to add project to workspace. It would be handy to have two additional checkboxes: -- Share project. Eclipse can automatically detect if there is CVS information available and enable checkbox. It can also provide additional pages in import wizard and those pages could be the same as used by "Share PRoject" wizard.
Sorry, I accidentaly hit sbmit button. Here is the rest: -- If there is an active "Working Set" selected (e.g. in active "Package Explorer" view), then Eclipse should enable another checkbox "Add to current Working Set: <name>" These options should make import more pleasant.
Option 2 is Bug 75539. I'll move this to Team as they handle all of the CVS support. As we provide the wizard we would likely have to rework some things to make this happen for them without touching CVS code.
Sorry - Bug 75339
Thanks Ted. Actually I wonder how all of this will integrate with non CVS VCS'es? There is Subversion plugin for Eclipse on tigris.org - http://subclipse.tigris.org/update It would be great if it can fit into the same infrastructure.
Yes any solution would need to be non-CVS specific and that is the major complication. There would need to be API added to the UI that would allow Team to register as a post-project import particpant. Team would then need to delegate to any registered repository provider types to test whether they though the project was sharable by them.
This would require the ability for Team (or individual repository providers) to participate in a project import. To cover all the cases and avoid user confusion, it would also require that creating a project over an existing folder in the file system also be treated as an import. The solution could be something as simple and specific as an import extension point that would ensure that any interested plugins were loaded and could process the delta to see if they should auto-share the project. Currently, we cannot rely on deltas since the CVS plugin may not be loaded when an import occurs. A more deluxe solution would be to have Import participants that can take part in the import wizard and potentially provide feedback through the import wizard when an import occurs. These concepts already exist in the ltk and may, someday, make it into the workbench. I'm moving this bug to UI because the mechanism to enable this needs to be provided by the workbench.
I'm marking this a duplicate of 36483. Although not technically a duplicate, the fix that I just submitted for that bug also fixes this one (i.e. Imported projects that contain CVS meta files will be auto-shared). *** This bug has been marked as a duplicate of 36483 ***
This is not really a dup of bug 36483. Bug 36483 only allows auto-sharing for team plug-ins that use with meta-files. ClearCase doesn't use meta-files. The ClearCase plug-in needs to check whether the project directory is located inside a ClearCase VOB or not. Thus, a callback API would be necessary.
