Bug 284082 - [UI] Provide "Export Team Project Set" action in CVS synchronization
Summary: [UI] Provide "Export Team Project Set" action in CVS synchronization
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows Vista
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-21 02:14 EDT by Eike Stepper CLA
Modified: 2019-09-06 15:32 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eike Stepper CLA 2009-07-21 02:14:16 EDT
It's great that I can (create a) branch from the Synchronize view. But often I need to mention this new branch in a bugzilla and usually I attach a PSF file for the branched projects. It would be nice to create this file directly from the Synchronize view, too.
Comment 1 Szymon Brandys CLA 2009-07-21 05:45:55 EDT
You could configure a key binding to create psf in any context (the package explorer, the sync view, etc.) and of course Import is available in the main menu.

We should keep a compromise between the context menu size and its usability. I believe that the right solution here is to fix bug 21219.

I'll wait for Paul's comment on it.
Comment 2 Eike Stepper CLA 2009-07-21 07:43:46 EDT
I think bug 21219 is a good thing by itself but would not help here. The main point about this request is that the selection of the projects to include into the PSF should be automated based on the "dirty" projects in the Synchronize view.

Honestly, the more I think about this, for my purpose I'd rather need something like a "Export PSF for projects with a certain CVS tag (like a branch)" action. I'm not sure if that would be appreciated by many users. What do you think?
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:32:52 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.