Community
Participate
Working Groups
In https://twitter.com/mickaelistria/status/1211224135763931138 its stated that eclipse <path> should open eclipse with import wizard. It does not. Makes it really tedious to open projects in Eclipse compared to other IDE's. p.s. I reported/commented on similar in past but wasn't able to find it in bugzilla ;/
On Mac, please try with the following command: open -a Eclipse.app /path/to/project The N&N entry also specifies the Mac command to be used - https://www.eclipse.org/eclipse/news/4.12/platform.php#pass-directory-to-launcher
(In reply to Lakshmi Shanmugam from comment #1) > On Mac, please try with the following command: > > open -a Eclipse.app /path/to/project > > The N&N entry also specifies the Mac command to be used - > https://www.eclipse.org/eclipse/news/4.12/platform.php#pass-directory-to- > launcher Does this work for you on Mac?
(In reply to Lakshmi Shanmugam from comment #2) > (In reply to Lakshmi Shanmugam from comment #1) > > On Mac, please try with the following command: > > > > open -a Eclipse.app /path/to/project > > > > The N&N entry also specifies the Mac command to be used - > > https://www.eclipse.org/eclipse/news/4.12/platform.php#pass-directory-to- > > launcher > > Does this work for you on Mac? This does indeed works. However, it's not consistent with the Windows/Linux equivalent, is confusing/less convenient for users. I believe IntelliJ and VSCode support simple "idea <path>" and "code <path>" commands on macOS.
that does work and is nice, any reason why on osx the eclipse binary itself does not allow this kind of usage ?
related issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=559075
fyi, for now I worked around this on osx by adding `/usr/local/bin/eclipse` that contains `open -a ~/java-latest-released/Eclipse.app $@` would be great if eclipse could offer to set this up on its own via a command.
bumped into this again - really would be nice if eclipse would help osx users to get a decent out-of-box behavior. Opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=567828 incase the installer is more suited for fixing this.
