Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 361216

Summary:	Implement org.eclipse.xtext.linking.impl.DefaultLinkingService.registerImportedNamesAdapter using an interface instead of an abstract class
Product:	[Modeling] TMF	Reporter:	Mark Christiaens <mark.g.j.christiaens>
Component:	Xtext	Assignee:	Project Inbox <tmf.xtext-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	christian.dietrich.opensource, mark.g.j.christiaens, sebastian.zarnekow
Version:	2.1.0
Target Milestone:	---
Hardware:	PC
OS:	All
See Also:	https://github.com/eclipse/xtext-core/pull/663
Whiteboard:	v2.14

Description Mark Christiaens

2011-10-18 04:21:28 EDT

Build Identifier: 20110916-0149

org.eclipse.xtext.linking.impl.DefaultLinkingService.registerImportedNamesAdapter checks whether scopeProvider is a AbstractGlobalScopeDelegatingScopeProvider.  This is a bit uncomfortable.  When implementing your own scope provider, you do not want to derive from the above abstract class.  However, when you do not derive from this class, then the imported names functionality is broken.

Please introduce an interface that indicates that the scope can be wrapped to intercept scope requests.  

Reproducible: Always

Comment 1 Eclipse Genie

2018-03-21 12:18:56 EDT

GitHub Pull Request 663 created by [szarnekow]
https://github.com/eclipse/xtext-core/pull/663
From: genie@eclipse.org
Subject: [Bug 361216]

@id = 361216
@see_also = https://github.com/eclipse/xtext-extras/pull/240

GitHub Pull Request 240 created by [szarnekow]
https://github.com/eclipse/xtext-extras/pull/240

Comment 2 Christian Dietrich

2018-03-21 14:14:48 EDT

fixed in 2.14