Community
Participate
Working Groups
using ./eclipse <path> or open -a ~/java-latest-released/Eclipse.app on osx today *always* opens the project from the filesystem wizard *even* if that project is already imported and opened in Eclipse. I'll argue it should only do so if it is *not* imported as its unnecessary and tedious having to close that dialog everytime you use this superuseful shortcut to open eclipse on your project. Reasons why *not* to open import on existing project: a) other editors/IDE's (intellij, vscode, emacs, vi, ..) does it that way - only tries to import something that is not already there. Other IDE's don't even ask questions - they just open it up. Thus eclipses approach is "heavy" in comparison. 2) Opening of a File (eclipse <path to specific file>) already behave like this. It does not open another editor if the file is already open. It reuses the same. Reasons *to* open import on existing project: 1) you might want to import additional projects there are as subfolders... But if this is your usecase then I say it is fine to manually go use the wizard rather than always opening the import wizard.
additionally the import wizard will actually just show an error in most cases as most projects won't have anything relevant to import except the project you already imported.
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.
