Move Class refcatoring broken in 3265?

After moving several classess from one package to another in the same source
tree references to moved classes were not updated
Have anyone experienced the same problem?


4 comments
Comment actions Permalink

Well, I'm aware of this bug in builds before 3265 in case you move the class
from a file with multiple classes.
However fixing this bug could lead to others, so if you can reproduce it,
please file a request to JIRA.

Eugene.

"Alex Roytman" <nospam@hello.world> wrote in message
news:d24vpj$k4f$1@is.intellij.net...

After moving several classess from one package to another in the same

source

tree references to moved classes were not updated
Have anyone experienced the same problem?

>
>


0
Comment actions Permalink

Yep, just happened to me as well. It kinda sucks to go through a heap of classes
and fix the imports. This happened with 3265 while trying to move a single class.

Eugene Vigdorchik (JetBrains) wrote:

Well, I'm aware of this bug in builds before 3265 in case you move the class
from a file with multiple classes.


What's "from a file with multiple classes" anyway? For me it is reproducible in
the very simple case like that:

-- file Test.java --
package test;
class Test {
Foo foo;
}

-- file Foo.java --
package test;
class Foo { }

Moving Foo to package test.util does not add the import statement to class Test.
Having "Add unambiguous imports on the fly" turned on may "fix" this magically,
so better turn it off to see the effect.

However fixing this bug could lead to others, so if you can reproduce it,
please file a request to JIRA.


Since this a total show stopper I'm afraid you have to take the risk of fixing it ;)
Here ya go: http://www.jetbrains.net/jira/browse/IDEA-1169

Sascha

0
Comment actions Permalink


"Sascha Weinreuter" <sascha.weinreuter@NOSPAM-cit.de> wrote in message
news:d28q4h$vm5$1@is.intellij.net...

Yep, just happened to me as well. It kinda sucks to go through a heap of

classes

and fix the imports. This happened with 3265 while trying to move a single

class.
>

Eugene Vigdorchik (JetBrains) wrote:

Well, I'm aware of this bug in builds before 3265 in case you move the

class

from a file with multiple classes.

>

What's "from a file with multiple classes" anyway?


That is:
class A{...} class B{...} ]]>

in one file:)

-- file Test.java --
package test;
class Test {
Foo foo;
}

>

-- file Foo.java --
package test;
class Foo { }

>

Moving Foo to package test.util does not add the import statement to class

Test.

Having "Add unambiguous imports on the fly" turned on may "fix" this

magically,

so better turn it off to see the effect.


Fixed, thank you.

Eugene.


0
Comment actions Permalink

Eugene Vigdorchik (JetBrains) wrote:
>>What's "from a file with multiple classes" anyway?


That is:
<code>
class A{...}
class B{...}
</code>

in one file:)


Ah, so it's also possible to move such classes now? Cool.

Fixed, thank you.


Thank you, that was incredibly fast :)

Sascha

0

Please sign in to leave a comment.