Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 360764 - [xtend] Report issue on duplicate unnamed extension fields
Summary: [xtend] Report issue on duplicate unnamed extension fields
Status: CLOSED FIXED
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.0.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: SR2   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-13 03:07 EDT by Jan Koehnlein CLA
Modified: 2017-09-19 18:02 EDT (History)
1 user (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-10-13 03:07:54 EDT 
The following code is compiled fine even though the second extension is unreachable unless you know its synthetic name "_string_1"

class XtendClass extends JavaClass {        
	@Inject extension String
	@Inject extension String
} 

Should we report an issue here? If so, error or warning?
Comment 1 Sven Efftinge CLA 2011-10-13 03:30:04 EDT 
Although I can't see a reason why one would want to have extensions of the same type twice it should be a warning. I think we can have that warning no matter there is a name or even two different names specified. Marking the extension keyword seems appropriate.
Comment 2 Jan Koehnlein CLA 2011-10-17 05:40:28 EDT 
I made it an error anyway ;-)

Pushed to MASTER
Comment 3 Karsten Thoms CLA 2017-09-19 17:51:55 EDT 
Closing all bugs that were set to RESOLVED before Neon.0
Comment 4 Karsten Thoms CLA 2017-09-19 18:02:39 EDT 
Closing all bugs that were set to RESOLVED before Neon.0