Bugzilla – Full Text Bug Listing
| Summary: | [Repo View] Cannot add new directory at CVS root level | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Marian Grigoras <mgrig> | ||||
| Component: | CVS | Assignee: | platform-cvs-inbox <platform-cvs-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P5 | Keywords: | helpwanted | ||||
| Version: | 3.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 2000 | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
|
Description
Marian Grigoras
What do you mean by root directory? Do you mean one that is created at the root level of the repository. For example, if my repo path is /home/cvsrepo, ae you trying to ad a directory /home/cvsrepo/newfolder? If so, how did you perform step 1) in your example? Yes, this is what I mean: repo path is /home/cvsrepo and I want to add /home/cvsrepo/newfolder. In my step 1 I checked out all existing directories in /home/cvsrepo (like /home/cvsrepo/lib, /home/cvsrepo/doc, etc). Of course I could not check out /home/cvsrepo/newfolder, as it was not yet there. At this point, I created in the Java perspective the newfolder (parallel to lib, doc, etc) and tried to add it to the repository. At this point I got the error message. This is supported in a round-about way. You can create the newfolder as a project and perform a Team>Share project. This will create the remote folder. You can then check it out into your main project. I hit this also, it's rather surprising: I have a project that has some subdirectories from one CVS repository, some from another CVS repository, so I use "Check out into existing project." When you look at how it's checked out, though, all the */CVS/Repository files are correct *except* the root one, which is set to "CVSROOT/Emptydir". It prevents you from adding anything to the root directory. Created attachment 29379 [details]
Add new folder in the CVS
I have got the same problem with CVS server on linux and eclipse Version: 3.2.0
Build id: I20051102-1600.
So what I have done:
- some CVS module "wdkWEB-INF" was checked out as a folder on the top eclipse
project level;
- a new folder "folder2" was created on the top eclipse project level;
- right click on the "folder2" -- "team" -- "Add to Version Control"
- a warning was shown "You have explicitly asked ... would have been ignored.
Continue ?" --> "OK"
- some msg was shown for a millisecond
- the .log file had:
!SESSION 2005-11-05 17:42:16.406
-----------------------------------------------
eclipse.buildId=I20051102-1600
java.version=1.5.0_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Command-line arguments: -os win32 -ws win32 -arch x86 -clean
!ENTRY org.eclipse.team.cvs.core 4 -10 2005-11-05 18:47:27.890
!MESSAGE The server reported an error while performing the "cvs add" command.
!SUBENTRY 1 org.eclipse.team.cvs.core 4 -14 2005-11-05 18:47:27.890
!MESSAGE test: cvs [server aborted]: cannot add to /cvsroot/<cvs project
name>/CVSROOT/Emptydir
The same CVS folder creation by use of a server CVS client succeeded, namely:
-- mkdir test
-- cd test
-- cvs checkout .
-- mkdir folder2
-- cvs add folder2
Directory /cvsroot/<cvs project name>/folder2 added to the repository
It appears so, as if
- either the eclipse project top level would be corresponded by default to
<CVS project>/CVSROOT/Emptydir/ but not to the <CVS project>/ as it has to be;
- or cvs add command was issued in the actual directory <CVS
project>/CVSROOT/Emptydir/ but not in <CVS project>/ as it has to be;
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. 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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie. |