Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350812 - [xbase] XbaseGeneratorFragment should bind an IQualifiedNameProvider
Summary: [xbase] XbaseGeneratorFragment should bind an IQualifiedNameProvider
Status: CLOSED FIXED
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.0.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: SR2   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 354596 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-06-30 08:21 EDT by Jan Koehnlein CLA
Modified: 2017-09-19 17:59 EDT (History)
2 users (show)

See Also:
jan: indigo+

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 Jan Koehnlein CLA 2011-06-30 08:21:23 EDT 
The default qualified name provider returns "null" for JvmGenericTypes. 
Inferred JVM elements will thus be indexed with a wrong qualified name.

If inferJvmModel is true, we should automatically generate an IQualifiedNameProvider similar to the one in the Domainmodel example.
Comment 1 Sebastian Zarnekow CLA 2011-08-12 05:18:33 EDT 
*** Bug 354596 has been marked as a duplicate of this bug. ***
Comment 2 Jan Koehnlein CLA 2011-09-12 10:33:52 EDT 
I needed this during refactoring:
  org.eclipse.xtext.common.types.xtext.JvmIdentifiableQualifiedNameProvider

We still have to bind it for Xbase languages
Comment 3 Sven Efftinge CLA 2011-09-19 05:00:18 EDT 
pushed to master
Comment 4 Karsten Thoms CLA 2017-09-19 17:47:57 EDT 
Closing all bugs that were set to RESOLVED before Neon.0
Comment 5 Karsten Thoms CLA 2017-09-19 17:59:05 EDT 
Closing all bugs that were set to RESOLVED before Neon.0