This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 179944 - Refactoring does not work with message "Cannot rename here"
Summary: Refactoring does not work with message "Cannot rename here"
Status: VERIFIED FIXED
Alias: None
Product: javafx
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 normal (vote)
Assignee: J Bachorik
URL:
Keywords: REGRESSION
Depends on:
Blocks: 173077
  Show dependency tree
 
Reported: 2010-01-28 02:10 UTC by Alexandr Scherbatiy
Modified: 2010-02-05 02:29 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandr Scherbatiy 2010-01-28 02:10:16 UTC 
Product Version         = NetBeans IDE Dev (Build 201001190201) (#4d62ab8d1fa1)
  Operating System        = Windows XP version 5.1 running on x86
  Java; VM; Vendor        = 1.6.0_15; Java HotSpot(TM) Client VM 14.1-b02; Sun Microsystems Inc.


Steps to reproduce:

- Create A class:
--------------  A.fx  ----------------------
public abstract class A{
    public var name:String = "A";
    public abstract function f():Void;
}
--------------------------------------------

- Create B class:
--------------  B.fx  ----------------------
class B extends A{
    override var name = "B";
    override function f() {
        println("H");
    }
}
--------------------------------------------

- Refactor -> Rename the 'f' function to 'g' in the A class

The message pops up: "Cannot rename here".
Comment 1 Alexandr Scherbatiy 2010-01-28 02:12:20 UTC 
From a message:
>> The NB 6.9 just shows the message "Cannot rename here" for these issues.
> This is caused by CSS refactoring gone wild - they eat all refactoring
> events :( They fixed it in their own team repository but thanks to NB
> build continuously failing it still  has not been propagated to
> main-golden :(
Comment 2 J Bachorik 2010-02-03 07:28:16 UTC 
This should have been resolved by the changes in CSS refactoring propagated to main-golden.
Comment 3 Alexandr Scherbatiy 2010-02-05 02:29:41 UTC 
verified in NetBeans-JavaFX-Soma: #143