Oxygen: Open Workspace menu item not showing #5282
Milestone
Comments
|
Thanks Brendan, In recent versions of Eclipse, the badge does not appear unless the workspace name has been set, this is due to a conflict with Oomph which I so far has been unable to resolve. See #5281 . If the menu item does not appear, the bundle has not been activated. I can confirm that it should work in both Neon and Oxygen as I use it daily. Maybe the logs will reveal something interesting. Would you mind adding the .log file to this report? Also make sure you're using Java 8 as this is required. |
|
I have the following workspace name set in
Is the log file |
|
|
It looks like you're using CDT, how did you install it? |
|
Using the new Eclipse installer. Nothing fancy at all. It does install in my home directory I also have I also have I installed OS X Launcher via Eclipse Marketplace, from within the running Eclipse Oxygen, so everything should have been installed the right place, yes ?? |
|
Well, I see nothing obvious. I'll try to reproduce by replicating your configuration. I just tested with a vanilla CDT from Neon.3 and the workspace launcher works just as expected. |
|
What build and version of the launcher plug-in are you using? |
|
Version 3.0.0 (according to Eclipse Marketplace). I downloaded the CPP Eclipse Oxygen package and installed in manually (copy to my home directory). I instlled OS X Launcher from Eclipse Market place (and restarted). The Open Workspace menu item now appears :) However the badge does not appear !! I opened Preferences => General => Workspace and the workspace name is present. I edited it (added an extra character), hit "apply" and "apply and close", and now the badge shows up. Restarting Eclipse and the badge disappears again (until I edit the name in the Workspace settings). Next, I ran Eclipse Oxygen installed via Eclipse Installer. The "Open Workspace" menu item does not appear, and the badge does not appear. I edited the workspace name and the badge now appears. I edited back to the original value, and the badge DISAPPEARS. Looks like there might be two separate issues (badge and menu). Also I the name the workspace is "lost" if it is of moderate length. e.g. "test-oxygen". I the text does not fit easily in the space. Is there a way to dynamically scale the badge font so it will fit and be readable by the user? |
|
Thanks for investigating. The missing badge is tracked in #5281. I have no idea why the menu item is disappearing as I'm unable to reproduce this. To verify that the plug-in is properly installed, go to Eclipse > About Eclipse > Installation Details and find the entry there. |
|
Both the Eclipse Installer eclipse instance and the manually installed eclipse instance show the the following in installed.
However, only the manually installed eclipse instance shows the |
|
OK, so when you say "Next, I ran Eclipse Oxygen installed via Eclipse Installer", what exactly did you install? |
|
|
Thanks, I'll try to reproduce. |
turesheim
changed the title
|
I belive these are two different issues. Tracking badge not showing in #5281 |
|
I'm unable to reproduce the issue with the Open Workspace menu item missing. The only thing I can think of that might cause this, is that somehow the plug-in is unable to start. I've looked at the dependencies and the only one that is clear, is the requirement for Java 8. I know the Eclipse installer likes to specify which JVM to use in eclipse.ini. Would you mind checking to see whether it's using something else than Java 8? |
|
The eclipse.ini file specifies java 1.8 jdk. Solved (but not sure why). I logged in as a different user, downloaded eclipse installer, installed cpp eclipse, installed os x launcher from Market Place, and it worked perfectly. I copied the eclipse.ini file to my login eclipse installation, but it had no effect. I speculated that maybe the installer downloaded a newer version of Eclipse or some plugins ?? (as they were done approximately 9 days apart). So I deleted the install directory, and reinstalled with a freshly downloaded installer. I then installed OS X Launcher and it worked perfectly. I then deleted the install and reinstalled, but then installed my usual plugins first (Vrapper, PyDev, Markdown Text Editor), restarted, then installed OS X Launcher. This is what I would have done originally. Again it worked perfectly. So, it seems to be fixed, but I don't really know why, other than maybe the original install was different for some reason. Thanks for taking the time to investigate. |
|
Just to let you know that you're not the only one having this issue: same thing here. MacOS Sierra, Eclipse Oxygen installed via Installer, latest launcher via Marketplace. I also tried eclipse -clean before installing the launcher, but made no difference. Haven't tried reinstalling Eclipse yet. |
|
Cool. If you don't have much luck, then I suggest totally uninstalling, download a new installer image, and reinstall. Good luck! It's been working fine for me since I did that. Hasn't missed a beat since. |
|
same issue here, installed Eclipse from installer, installed launcher from Marketplace but I can't see the Open Workspace menu |
|
The plug-in does not do anything weird, so the only thing I can think of is that something is preventing it from starting. One way of verifying this is to go to the running Eclipse instance, Console, local pull down menu and select Host OSGi Console. Run the command ss, locate net.resheim.eclipse.launcher.core and net.resheim.eclipse.launcher.macosx and make note of the number. Run the diag command. For example: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've installed Eclipse Launcher to Eclipse Oxygen installation, running macOS Sierra 10.12.5. Eclipse was installed using the new Eclipse Installer.
There is no "Open Workspace" menu item, as there used (e.g. Mars or Luna worked ok). It doesn't work for Neon either.
There is no Badge in the dock icons (or when command-tabbing). Do Badges appear if there is only one instance or only if there are 2+ instances of Eclipse running?
The text was updated successfully, but these errors were encountered: