Open bugs in Idea 4.0
It would be really nice to have all bugs related to refactorings closed in the 4.0 final. It is the 'core' functionality and it is kind of unpleasant to feel that some basic stuff like 'extract method' can actually break your code..
One can live with other minor drawbacks that are harmless to the code, like 'ridiculously looking dialogs' etc...
Please sign in to leave a comment.
Igor Karpov wrote:
What are the most annoying for you?
BTW, I am afraid one can never fix all the bugs...
Friendly,
Dmitry
--
Dmitry Lomov
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"
I know, you have not asked me, but for me these are:
1. 11153
2. 2885
3. 3551
Tom
Thomas Singer wrote:
>> What are the most annoying for you?
Me neither, but since the question was asked:
http://www.intellij.net/tracker/idea/viewSCR?publicId=26128
http://www.intellij.net/forums/thread.jsp?forum=13&thread=69766
http://www.intellij.net/forums/thread.jsp?forum=15&thread=64710
http://www.intellij.net/forums/thread.jsp?forum=15&thread=62118
and PLEASE open up the J2EE API.
Thanks
R
Guys,
Igor have been talking about refactoring bugs.
Friendly,
Dmitry
--
Dmitry Lomov
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"
He does not only not asked you, but even not asked for any bugs not related to refactoring :)
But among them only the first one is about refactoring. We were discussing
bugs in refactorings.
--
Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Thomas Singer" <nomail@nodomain.com> wrote in message
news:bv347v$2k6$1@is.intellij.net...
>
>
>
How about 9572? It's been open with high priority for quite a while (albeit
marked as a feature).
Thx,
Andrei
Well, and I was talking about most annoying bugs :P
Tom
Thomas Singer wrote:
>> Igor have been talking about refactoring bugs.
hehe +1
:)
R
BTW, there is a crowd of refactoring bugs related to visibility (e.g.
"move" an inner class to a top-level class that used private methods of
the outer class), but since I can fix it myself easily and creating a
reproducible example is often not that easy, there might not be some
tracker requests for it.
Tom
In article <bv3318$n43$1@is.intellij.net>,
"Dmitry Lomov (JetBrains)" <Dmitry.Lomov@jetbrains.com> wrote:
This one:
http://www.intellij.net/tracker/idea/viewSCR?publicId=12815
"If you use the "Move" refactoring to move the last class out of a
package, import statements in other classes that refer to that now-empty
package are not removed, resulting in compiler errors ("the package does
not exist")."
(Note that is can cause hundreds of compiler errors, which can be a pain
to fix.)
Why not?
Erik Hanson wrote:
>> BTW, I am afraid one can never fix all the bugs...
Were you ever able to? :)
Friendly,
Dmitry
--
Dmitry Lomov
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"
In article <bv3m3u$p0l$2@is.intellij.net>,
"Dmitry Lomov (JetBrains)" <Dmitry.Lomov@jetbrains.com> wrote:
Yes, but I mostly write applications for internal corporate use, so they
are smaller and simpler than IDEA and have fewer users. That's probably
the reason why we generally don't get too many bug reports and why we
are able to fix the bugs we do get quickly.
Perhaps when a program reaches a certain size, it just becomes too much
work to write all the tests and fix all the bugs and it's more
economical to just ship with a few bugs.