Bug 354600

Description Vladimir Piskarev 2011-08-12 06:38:20 EDT

Build Identifier: I20110613-1736

For nested types the DeltaConverter produces NameBasedEObjectDescriptions with incorrect QualifiedNames. 

Namely, for a given nested type its QualifiedName as reported by DeltaConverter will be different from its QualifiedName as seen by scope provider. For example, for nested type 'example.Foo.Bar' the DeltaConverter will report its name as [example][Foo][Bar] while the scope provider treats it as [example][Foo$Bar].

It follows, that the 'importedNames' corresponding to the referred nested types in a resource description will never match the 'exported names' of those same types as reported by DeltaConverter. Therefore, in certain cases the set of resources affected by Java changes may not be computed correctly, which will result in (incremental) build problems being incorrectly reported.

Reproducible: Always

Steps to Reproduce:
1. Import the attached 'org.xtext.example.domainmodel' and ''org.xtext.example.domainmodel.ui' projects into the workspace

2. Run the runtime workbench and import the attached 'example' project into the runtime workspace. Note the build problem "Couldn't resolve reference to JvmType 'example.Foo$Baz'" in Foo.dmodel

3. Open 'Foo.java' and change 'Bar' to 'Baz'. Save the change. Note the build problem still persists.