(eclipse) renaming class file does not rename source
Migrated from http://lampsvn.epfl.ch/trac/scala/ticket/380
Reporter gavinbong
In eclipse 3.3.1.1 with the latest plugin (installed via update site); do the following to reproduce:
Reporter gavinbong
In eclipse 3.3.1.1 with the latest plugin (installed via update site); do the following to reproduce:
- Create a scala class e.g. Foo.scala * Right click on the new artifacts, choose refactor>rename and call it Fool You will notice that the filesystem now contains Fool.java but internally the source still has class Foo.
Leave a comment
on 2008-01-16 03:54 *
By tracImporter
Trac author: gavinbong
My bug report has a small mistake. For the last line, do substitution: s/Fool.java/Fool.scala
My bug report has a small mistake. For the last line, do substitution: s/Fool.java/Fool.scala
on 2008-01-16 09:19 *
By tracImporter
Trac author: mcdirmid
Yep. Whenever someone puts a refactoring engine in place we can implement this right. Aint gonna be me though.
On the other hand, this is perfectly ok in Scala: the class does not have to correspond to the source code. So maybe we could change to "won't fix"?
Yep. Whenever someone puts a refactoring engine in place we can implement this right. Aint gonna be me though.
On the other hand, this is perfectly ok in Scala: the class does not have to correspond to the source code. So maybe we could change to "won't fix"?
on 2008-01-21 04:57 *
By tracImporter
Trac author: washburn
If the intended behavior is to rename the file, then this is not a bug. If the intended behavior is to rename uses of the class', then this is a bug. However, even if the latter is the correct interpretation it sounds like Eclipse is providing the wrong user interface, because it does not sound like there is a way to rename a class
If the intended behavior is to rename the file, then this is not a bug. If the intended behavior is to rename uses of the class', then this is a bug. However, even if the latter is the correct interpretation it sounds like Eclipse is providing the wrong user interface, because it does not sound like there is a way to rename a class
Foo that appears in a file Bar.
on 2008-05-28 01:44 *
By tracImporter
Trac author: djspiewak
The convention I follow with Scala (and I assume is relatively common) is to house a single class/[object] pair in each file, named after the simple class name. For times when multiple classes are called for in a single file (sealed classes, trivial cases, etc), I switch to lowercase and usually use something plural. At any rate, this is beside the point.
I would propose that if the class being renamed shares a name with its containing file, then we should assume that one is named after the other and keep them in sync. Otherwise, just rename the class and ignore the file. I think this would be fairly sane behavior and something most people would expect.
The convention I follow with Scala (and I assume is relatively common) is to house a single class/[object] pair in each file, named after the simple class name. For times when multiple classes are called for in a single file (sealed classes, trivial cases, etc), I switch to lowercase and usually use something plural. At any rate, this is beside the point.
I would propose that if the class being renamed shares a name with its containing file, then we should assume that one is named after the other and keep them in sync. Otherwise, just rename the class and ignore the file. I think this would be fairly sane behavior and something most people would expect.
on 2008-07-31 03:31 *
By
I can only make sense of this as a request for a rename refactoring. It's planned, but as Sean implies it'll be a big job.
Updating tickets (#1000069, #1000195, #1000213, #1000223, #1000006, #1000021, #1000038, #1000048, #1000051, #1000052, #1000075, #1000103, #1000109, #1000115, #1000119, #1000156, #1000186, #1000207, #1000238, #1000262, #1000263, #380, #389, #683, #1238, #1331, #1635, #1645, #1715, #1729, #1744, #1783, #1839, #1869, #1885, #1890, #1902, #1918, #1919, #1924, #1925, #1946, #1964, #1991, #2131, #2233, #2342, #2348, #2408, #2459, #2499, #2523, #2572, #2582, #2602, #2614, #2615, #2675, #2710, #2745, #2763, #2816, #2830, #2834, #2878, #2879, #2887, #2888, #2901, #2911, #2912, #2922, #2937, #2938, #2942, #2951, #2955, #2957, #2961, #2964, #2965, #2974, #2975, #2989, #2990, #3002, #3055, #3070, #3087, #3135, #3139, #3173, #3182, #3184, #3200, #3213, #3214, #3221, #3243, #3251)
on 2011-03-24 13:18 *
By Iulian Dragos
Updating tickets (#1000199, #1000200, #1000201, #1000204, #1000205, #1000209, #1000210, #1000211, #1000212, #1000215, #1000217, #1000218, #1000220, #1000222, #1000226, #1000227, #1000228, #1000230, #1000231, #1000232, #1000233, #1000235, #1000236, #1000237, #1000239, #1000240, #1000241, #1000242, #1000243, #1000244, #1000248, #1000249, #1000252, #1000253, #1000254, #1000255, #1000256, #1000258, #1000259, #1000032, #1000059, #1000062, #1000163, #1000197, #1000216, #1000221, #1000224, #1000121, #1000175, #1000219, #1000251, #1000069, #1000195, #1000213, #1000223, #1000006, #1000021, #1000038, #1000048, #1000051, #1000052, #1000075, #1000103, #1000109, #1000115, #1000119, #1000156, #1000186, #1000207, #1000238, #1000262, #1000263, #380, #389, #683, #1238, #1331, #1635, #1645, #1715, #1729, #1744, #1783, #1839, #1869, #1885, #1890, #1902, #1918, #1919, #1924, #1925, #1946, #1964, #1991, #2131, #2233, #2342, #2348, #2408)
