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

Bug 346242

Summary:	[Xtend2] @Inject extension referencing to a non existing file is not marked as error
Product:	[Modeling] TMF	Reporter:	Joerg Reichert <joerg83reichert>
Component:	Xtext	Assignee:	Project Inbox <tmf.xtext-inbox>
Status:	VERIFIED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	sebastian.zarnekow, sven.efftinge
Version:	unspecified	Flags:	sven.efftinge: indigo+
Target Milestone:	SR1
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Joerg Reichert

2011-05-18 09:36:59 EDT

Build Identifier: Eclipse 3.6.2 M20110210-1200, Xtext 2.0.0.v201105171404

the Xtend2 editor validator should point out whether the reference to the injected extension file can be resolved.

Example: MyDslGenerator.xtend defines @Inject extension GeneratorExtensions generatorExtensions. When renaming the file GeneratorExtensions.xtend in GeneratorExtensions2.xtend there is no error marker shown in the editor of MyDslGenerator.xtend.  In contrast to that, referencing to an injected Java class file, that does not exist, is recognized. 


Reproducible: Always

Steps to Reproduce:
1. Create A.xtend
2. type @Inject extension B b (where there is no B.xtend in the classpath)
3. b should be marked as error but it isn't

Comment 1 Sebastian Zarnekow

2011-07-31 10:00:26 EDT

I cannot reproduce this one. I get an error marker for B. Why do you expect 'b' to be underlined, too?

Comment 2 Joerg Reichert

2011-08-01 10:10:36 EDT

It was not an issue with big or low b marked as an error, last time I tested it, there was no error marker at all. But this has been obvious fixed in the meanwhile, so this bug is verified.