Bug 370135

Description Ed Merks 2012-01-30 10:11:38 EST

This appears to be a general problem with Xtext's support for rename refactoring. I have the same problem in Xcore as I see in Xtend... 

Consider what happens when you have two Xtend files in two different packages.

package com.example

class Foo {
}

and 

package com.example.a

import com.example.Foo

class A  extends Foo {
}

If you rename Foo to FooBar, you end with with A like this:

package com.example.a

import com.example.FooBar

class A  extends com.example.FooBar {
}

When I look at how this works in the underlying framework, the rewrites are collected for preview purposes before they are applied to the real resources or model instances.  So when the reference to FooBar is serialized in A, there is no import for it yet, i.e., the old "import com.example.Foo" doesn't help to convince the serializer to produce FooBar rather than com.example.FooBar.