Bug 152186 - [Project Sets] Allow importing of team project sets right from Repository Exploring view
Summary: [Project Sets] Allow importing of team project sets right from Repository Exp...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-07-28 14:07 EDT by Mark Melvin CLA
Modified: 2019-09-06 16:18 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Melvin CLA 2006-07-28 14:07:33 EDT 
Eclipse 3.2 added a cool and useful feature where you can right-click a .psf file and import it directly (very nice!).  However, since us users are never happy, it would be really cool if you didn't have to check out the team project set file into your workspace in the first place.  ;o)  
It would be really neat to be able to import a .psf file right from the CVS repository explorer window, avoiding this extra checkout.  If there is a way to do the equivalent of this and I am just missing it - please let me know.
Right now we typically check out our .psf files into a dummy project - import them, then delete the dummy project.
Comment 1 Bogdan Gheorghe CLA 2006-08-01 13:53:54 EDT 
Sounds like a good idea - not sure if we have the manpower for 3.3 to do this but I'm going to set the target to 3.3 for now. Patches would be gratefully accepted!
Comment 2 Michael Valenta CLA 2006-08-17 10:52:20 EDT 
We do not plan on addressing this issue in 3.3.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:18:05 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.