Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350486 - mark occurences in grammar editor throws Error
Summary: mark occurences in grammar editor throws Error
Status: CLOSED FIXED
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.0.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-27 14:42 EDT by Stephan Herrmann CLA
Modified: 2017-10-31 10:59 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Herrmann CLA 2011-06-27 14:42:37 EDT 
When I enable mark occurences in Xtext's grammar editor each selection
event causes the following Error

org.eclipse.xtext.ui.editor.findrefs.EditorResourceAccess  - org.eclipse.ui.PartInitException: Factory org.eclipse.jdt.ui.internal.JarEntryEditorInputFactory returned null from createElement for editor id=org.eclipse.ui.DefaultTextEditor name=XMLNamespace.ecore

I can't see anything fancy in this project/file, it was started from scratch,
i.e., not against any existing model etc.

Interestingly, the error is logged under the plug-in ID org.apache.log4j.
Comment 1 Holger Schill CLA 2011-10-13 08:05:43 EDT 
Cannot reproduce the issue with the current head.
Could you please try again with the latest nightly?

Thanks.
Comment 2 Stephan Herrmann CLA 2011-10-13 08:45:04 EDT 
(In reply to comment #1)
> Cannot reproduce the issue with the current head.

Have you tried to reproduce with 2.0.0?

> Could you please try again with the latest nightly?

Sorry, no, I'm currently locked to 2.0.0, mainly due to reasons of building with
maven. If Xtext builds were published to a well-known maven repository on a
regular basis I could update to newer version more easily. That'd be a real
treat actually :)

Also, more than 3 months after reporting I wouldn't have the context to replay
what exactly happened back then -- no more than what I wrote in the bug.
Comment 3 Sven Efftinge CLA 2012-11-21 08:59:56 EST 
seems to be fixed
Comment 4 Eclipse Webmaster CLA 2017-10-31 10:48:52 EDT 
Requested via bug 522520.

-M.
Comment 5 Eclipse Webmaster CLA 2017-10-31 10:59:55 EDT 
Requested via bug 522520.

-M.