Community
Participate
Working Groups
The use case is as follows: I am working on a branch, with several projects checked out from that branch. I need to add a new project to go along with the others and commit it to CVS. Because my work is on the branch, I need to be able to add the new project to CVS on the branch (not on HEAD), but the Eclipse Team > Share Project wizard does not support that. Command-line and WinCVS (and probably other clients) allow you to do this; currently we have to resort to WinCVS to accomplish this unless we want to first add the new project to HEAD and then move it to the branch (which, aside from being a pain in the neck also makes future merges from branch to HEAD more problematic). Basically, the Share Project wizard should offer the user the opportunity to select either HEAD or an existing Branch on which to add the new project.
Note: this is somewhat related to Bug 238877 but the difference is significant. Bug 238877 talks specifically about a regression when associating a project with an existing module, while my scenario deals with an entirely new project that is not yet in CVS.
What would you expect to happen with such a project when you do "Replace with Another Branch or Version > HEAD" on it?
(In reply to comment #2) > What would you expect to happen with such a project when you do "Replace with > Another Branch or Version > HEAD" on it? > I'm not sure. What does Eclipse do currently if you try that on any file or project that exists on a branch but not on head? Even without the answer to that question, I'd think a reasonable approach woule be a message to the user about the situation and either fail/abort the replace or end up removing the project contents locally (if that can be done and still maintain the "CVS shared" state). Whatever command-line CVS does should be the model to follow, right?
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.
