| Summary: | [Import/Export] Allow for importing folder from the file system that is not an Eclipse project | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Brad Reynolds <bradleyjames> |
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
| Status: | RESOLVED WONTFIX | QA Contact: | Prakash Rangaraj <prakash> |
| Severity: | enhancement | ||
| Priority: | P5 | Keywords: | helpwanted |
| Version: | 3.4 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Brad Reynolds
So you would want the project creation to happen then as well? If there is no project to import into then there is currently no way to represent an unbound folder in Eclipse. How does Subclipse get around this then? What I'm wanting is exactly what I get from Subclipse, except from the file system. I want to checkout a folder and have it be a folder in Eclipse. I'm guessing the CVS support would allow for this as well but I haven't tried. After taking a second look, it looks like Subclipse does check it out as a project. It creates a .project file in the folder that was checked out. The "Exising Projects into Workspace" import wizard, as the name says, needs the project to be present already. If you want to create a new project, then you should use the New Project wizard. In the first page of the wizard, uncheck the 'Use default location' and point to the folder that you have already checked out. That should do the trick. The import wizard will not create .project files. |