Sadly, I can't reproduce this issue. Did this happen only for FooBar or also for other classes? Can you show the content of FooBar? Maybe there is something in there our refactoring tools do not like.

Hi Simon,

I tried to reproduce this Bug with this minimal example class structure:
com.test.foo.Foo.scala
com.test.bar.Bar.scala
com.test.Test.scala

In Test.scala there was a Test class and a Test object. In this Test object I had a case class that is used in Bar or/and Foo, so Import this case class to Foo or/and Bar and then rename the Test class with your context menu. Afterwards your case class imports are broken.

Ok, I can reproduce it now.

Code example:

// file 1
package com.test

object Test1 {
  class Class
}

// file 2
package com.test.bar

import com.test.Test1.Class

class Bar {
  def x: Class = ???
}

After renaming Test1 to Test2, the import in file2 is broken:

package com.test.bar

import com.test Test2.Class

class Bar {
  def x: Class = ???
}

See https://github.com/scala-ide/scala-refactoring/pull/109

Don't break imports when renaming objects

Fixes #1002537

Branch: master
Commit: scala-ide:5478748f31