Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 179783

Summary: [Wizards] CVS Directories not being created when checking out into existing project
Product: [Eclipse Project] Platform Reporter: Rodney S. Foley <aalst>
Component: CVSAssignee: platform-cvs-inbox <platform-cvs-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: major    
Priority: P3 Keywords: helpwanted
Version: 3.2.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Rodney S. Foley CLA 2007-03-28 12:20:17 EDT
Build ID: M20070212-1330

Steps To Reproduce:
1. Create a normal Java Project 
2. Go to the CVS Repositories perspective 
3. Go to a folder and right click on it and select "Check Out As" 
4. In the dialog select "Check out into an existing project" and click next 
5. Select the java project created in step 1 and click finish 
6. After it completes the check out go to the Java Perspective and there will not be any CVS Icon Decorations on the project or on the new folder you checked out under the project. 
7. Go to the Projects properties and there will not be any CVS item in the left panel 
8. Go to the projects location in the local file system and there will not be any CVS folders anywhere in the project 

More information:
I am using Eclipse 3.2.2 with a majority of the Calisto Eclipse plugins, and no 3rd party plugins on Windows XP SP2. It is a fresh install from the currently posted eclipse-SDK-3.2.2-win32.zip file. Then I used the update to get most of the Java related Callisto products. Didn't tweak any default preferences on a newly created workspace. I did all this because I though I may have had some conflicting plugins or something or wacky preference settings.

This issue can be recreated consistently within a workspace on specific projects, while other projects work fine. The bizarre part is that when create a new workspace and start setting it up the same way the projects that have this problem change. However within the workspace the issue can be recreated on these projects consistently. 

Now I can delete the project and start over as many times as I want and it will be the same result for this project. Even if I change the name of the project but keep checking out the same CVS folder the problem continues. 

If I check out a different folder to this project it works find. 

As I stated above the bizarre thing is that the projects with the problem only are repeatable within the current workspace. If I create a new workspace and start over I will get have the same problem but with different projects. 

The other methods of checking out work fine it seems to be isolated to the "Check out into an existing project" method. However this is the method I have to use to get all my projects set up correctly with the correct dependencies because of how our CVS folders where organized a long time ago, and we cannot really change them any time soon. 

So please if anyone has seen this issue before and has a solution or if anyone has suggestions please let me know. However please do not tell me to not do it this way because I have to do it in this manner. This method should work and does most of the time it however doesn't work just enough to make it very annoying.
Comment 1 Rodney S. Foley CLA 2007-03-28 12:28:25 EDT
A workaround I just discovered:
If this happens per the steps to reproduce above if repeat the steps except instead of selecting the folder that has the problem you select any folder from CVS except the one experiencing the problem or any fold in it hierarchy chain. Then after it is checked out into the project, the project accepts it and shows its Icon Decorations and so forth. I then delete it from the project and repeat the steps again this time getting the folder that was having the problem. Now after it is checked out it works as expected.

This is strange and I shouldn't need to do this. It must be resetting whatever is wrong in the project.
Comment 2 Jerome Lanneluc CLA 2007-03-28 13:01:27 EDT
Moving to Platform/CVS
Comment 3 Michael Valenta CLA 2007-03-28 13:16:46 EDT
Is there any errors in the error log (or the PDE Runtime>Error Log view)?
Comment 4 Michael Valenta CLA 2007-04-10 14:22:35 EDT
Marking a REMIND. Please reopen with the requested information.
Comment 5 Rodney S. Foley CLA 2007-04-11 02:27:48 EDT
There where no errors that I could find in the log. The CVS console had a lot of warnings about the $LOG$ tag, but still got the file. No errors in the CVS console either. 

Four pieces of new information.  

1. This is now reproducible on the same CVS folder hierarchy by multiple users on different computers with slightly different installs of eclipse (3.1.x and 3.2.x)

2. The work around I posted didn't work consistently. It actually just worked a few times.

3. When digging deeper we noticed that the CVS folders are being created but only at a certain point and lower, they are not being creating all the way up the hierarchy to the project folder.  It turns out that the CVS folders start at the location we checked CVS folder into. Normally on all the other projects it creates the CVS folders from the project folder all the way down the source hierarchy.  However in these few cases it only creates it from the folder we check out on down.

4. A work around that we figured out that worked on each computer repeatedly was that if we copy the CVS folders from a working project that has the same "base" hierarchy to the project that doesn't work that Eclipse will start recognizing the project as a CVS controlled project.
Comment 6 Michael Valenta CLA 2007-07-16 16:01:00 EDT
I haven't been able to reproduce this. Are you able to reproduce it with a basic install of the Eclipse SDK or does it only happen when you have other plug-ins installed?
Comment 7 Eclipse Webmaster CLA 2019-09-06 16:12:29 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.
Comment 8 Eclipse Genie CLA 2021-09-21 16:47: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. 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.