Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 49522 - Source control folders should not be visible in package view
Summary: Source control folders should not be visible in package view
Status: RESOLVED DUPLICATE of bug 21128
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-05 06:58 EST by Andrew Premdas CLA
Modified: 2004-01-06 09:40 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Premdas CLA 2004-01-05 06:58:04 EST
When using folder based source control e.g. CVS and Subversion, the CVS 
folders appear in the package view of the application. I'll try and do a 
simple ACSII drawing of this

Assuming your source is in src you get 


+ src
  + CVS                - empty
  + foo.CVS            - empty
  + foo.myPackage      - has content
  + foo.myPackage.CVS  - empty

All the CVS entries should not be present, they should be ignored as they're 
not valid packages. Same applies to .SVN folders if your using subversion. You 
probably should be able to configure eclipse to tell it what files to ignore.
Comment 1 Michael Valenta CLA 2004-01-05 13:33:59 EST
The CVS folders are hidden but there are some known problems. How did you 
populate your workspace from CVS? Did you use an external tool to checkout the 
CVS projects and them import them? This is currently the only known case that 
postentially results in visible CVS folders. Could you provide us with the 
steps you took to get the failure so we can determine if yours differs?
Comment 2 Andrew Premdas CLA 2004-01-06 05:44:27 EST
source populated using standalone CVS client (Tortoise CVS) connecting to my 
CVS server which is CVSNT. Platform is Windows XP. Any further questions? 
Comment 3 Michael Valenta CLA 2004-01-06 09:40:29 EST
This is a known issue. The work around is to ensure that the CVS plugin is 
loaded before importing a project into Eclipse. You can do this but opening 
the CVS Repositories view or any other CVS view.

*** This bug has been marked as a duplicate of 21128 ***