Bug 275692 - Import of CVS module fails to place new project in desired working set
Summary: Import of CVS module fails to place new project in desired working set
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.4.2   Edit
Hardware: PC Linux-GTK
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-11 13:23 EDT by Jason Craig CLA
Modified: 2019-09-06 15:35 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Craig CLA 2009-05-11 13:23:26 EDT
Build ID: M20090211-1700


Steps To Reproduce:
1. Choose File/Import... and select "Projects from CVS".
2. Enter repository details and a module name to check out (module must not have a .project file in it).
3. Make sure "Check out as project configured using the New Project Wizard" is selected and check "Add project to a working set" and select a working set with the browse button.
4. Click next and proceed to set the project up with a wizard.  My project e.g. is a PHP project.
5. Once finished setting up, the CVS-synced PHP project is created but it is not placed in the working set you requested.


More information:
That's really all there is to it.  I've noticed that some of the project wizards have their own "add to working set" option (like the "General/Project" wizard) and in this case the project is added to the working set(s) specified within that wizard.  However, IMO whether you want a new project placed in a working set should be decoupled from the project type, different project types shouldn't offer placement in a working set while others do not.  The main point however is that the CVS import working set option doesn't seem to ever work.

I've tested this on Linux x86_64 and Windows XP, both have same build ID of Eclipse.
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:35:12 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.