Community
Participate
Working Groups
What steps will reproduce the problem? 1. I have a Java project in my workspace. It is not an XText project. 2. Do a right click to open context menu for the project. 3. Error below is logged. -- Error Details -- Date: Tue Apr 04 09:32:04 CEST 2017 Message: Plug-in 'org.eclipse.xtext.ui.shared' contributed an invalid Menu Extension (Path: 'org.eclipse.ui.projectConfigure' is invalid): org.eclipse.xtext.builder.action.AddXtextNatureAction Severity: Error Product: Eclipse Platform 4.6.3.v20170301-0400 (org.eclipse.platform.ide) Plugin: org.eclipse.ui Session Data: eclipse.buildId=4.6.3.M20170301-0400 java.version=1.8.0_121 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US Framework arguments: -showlocation Command-line arguments: -os win32 -ws win32 -arch x86_64 -showlocation
Is this are normal eclipse or an RCP? Can you share your plugin list?
Do you have a complete error trace?
(In reply to Christian Dietrich from comment #2) > Do you have a complete error trace? No. the error details from error log is all I have. It is not necessary to have a Java project. It happens also for a project with this .project file: <?xml version="1.0" encoding="UTF-8"?> <projectDescription> <name>location_view</name> <comment></comment> <projects> </projects> <buildSpec> </buildSpec> <natures> </natures> </projectDescription> When I do the first right click to open the context menu, the error happens, but the context menu does not open. On the second click the context menu opens and the error does not appear.
i am wondering how to reproduce this. downloaded neon3 + installed xtext and dont get this error
Created attachment 267647 [details] List of plugins in my installation
(In reply to Christian Dietrich from comment #1) > Is this are normal eclipse or an RCP? > Can you share your plugin list? This is a normal Eclipse, no RCP. The plug-in list is in the attached plugin list.zip.
Is this helpful: https://bugs.eclipse.org/bugs/show_bug.cgi?id=218593 ?
unfortunately i cannot reproduce this. i see there is a ton of similar issues, but they should be fixed (in platform, not xtext)