Bug 560588 - [Import/Export] Import project doesn't respect the project name when workspace is at the top level
Summary: [Import/Export] Import project doesn't respect the project name when workspac...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 4.14   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-27 04:46 EST by Greg Byrne CLA
Modified: 2020-02-27 06:55 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Byrne CLA 2020-02-27 04:46:30 EST
## Problem

Importing existing projects into eclipse do not respect the Project name as defined in the .project file depending on when the workspace is located in the code's top level directory.

## Reproduce
0. Pull down the git repository at https://github.com/byrne-greg/EclipseBug
1. Open Eclipse
2. Switch the workspace to the /EclipseBug/ directory
3. Select from Eclipse top menu File -> Import -> General -> Existing projects into workspace
4. Use the current directory (/EclipseBug/) as the root directory and ensure Search for nested projects is selected
5. The projects that should be displayed are CoreInf and NotCoreInf (as expected, using the .project name)
6. Switch the workspace to the /EclipseBug/myWorkspace/ directory
7. Select from Eclipse top menu File -> Import -> General -> Existing projects into workspace
8. Use the current directory (/EclipseBug/myWorkspace/) as the root directory and ensure Search for nested projects is selected
9. The projects that should be displayed are CoreInf and coreinf (not expected, using the directory name)

## Result
### Expected
When the workspace is set to the top level directory of the projects, Eclipse should import using the project name rather than the subdirectory name of the project.

## Workaround
Ensure your workspace is at a level where imported projects are not nested one level deep (i.e. set your project at least two levels above the codebase)
Comment 1 Greg Byrne CLA 2020-02-27 05:01:53 EST
I have found this behaviour in 4.14, 4.13, and back in March 2018 Oxygen 3 release.