Import options often less well understood

[kapinnow]

While working with any sort of import/export it seems often less understood which import function to use and how to configure it.
This is especially the case, if more than one project are stored in the filesystem under one root folder. Importing that root folder than may lead to trouble with the projects. One may choose e.g. to import a project under an existing project which may generate a couple of unwanted consequences.
Import from the file system for instance requires a folder to be selected for import and not the root one:

Also, it is not possible to create a subfolder of the root:

[deyabhik]

Hi @kapinnow ,

The import project workflows you mentioned above are from eclipse platform as is.
We cannot override this but only implement a separate one which does the same thing but in simplified way.

For now i recommend that you always take this path which is most reliable
File > Import > Existing Projects Into workspace
Here either chose an archive or a folder on disk which contains the ascet projects with a .project file.

Generally a good practice is to always use a separate workspace for each project context. By project context i mean a group of ASCET projects which belong logically together like Commons, SystemLib, YourAppProject
Also on the disk have one parent folder under which the project context projects are children and belong logically together.

Best Wishes
ASCET Team