Bugs I can't live with in the first 8.0 release Follow
Its that time in the release cycle to gather up our biggest issues and let JetBrains know what concerns us. Please post a list of the JIRA bugs you pray get fixed before release.
Please sign in to leave a comment.
First, Diana still needs some serious performance work. It starts up fast, alright, projects load faster than ever, alright... but editing is painfully slow. Typing feels sluggish, and intention actions takes ages to load. There are many open issues about this, and lots of cpu snapshots.
Oh, the settings panel is also completely borked in the latest release, but that's probably going to fixed soon, if not already.
Posting JIRA ticket numbers would help alot fixing exactly the issues which annoy you most :)
Here is my list of outstanding bugs. I will fill in the other thread with
things considered "features"
IDEA not reparsing JAVA code properly and highlighting code in the gutter as
red when it's compilable
Validating spring and persistence units on compile for a small module with a
few spring xml files takes 66 seconds per compile
Spring web flow 2.0 support is incorrectly highlighting "redirect" and
"forward" in view name
URLs in JSPs that reference a webflow are marked as an error
Adding each new JARs/source JARs to a library brings the user back to the
root of the drive instead of the last folder user was browsing
Project Path variable description not saved
This one is a biggie: Last few builds of IntelliJ aren't parsing SVN history
and update status properly
"Jon Steelman" <email@example.com> wrote in message
The following two are show-stoppers for me at the moment:
Refactored package by dragging it from one package to another and got a PSI
JPA incorrectly identifying entity reference has not being an entity
When the same table exists in multiple schemas, IDEA is incorrectly
validating @JoinTable mappings in JPA
"Grant Gochnauer" <firstname.lastname@example.org> wrote in message
>> Its that time in the release cycle to gather up our biggest issues and
>> let JetBrains know what concerns us. Please post a list of the JIRA bugs
>> you pray get fixed before release.
where do we submit bug reports? IDEA:Feedback or IDEA:Development?
"Develop with Pleasure!"
Compiler test output not being copied. all my test source dirs should be copied to the test output dir. i have my compiler resource patterns set as ?. (thats questionmark-star-dot-star)
IDEA:Feedback and then they sometimes get moved to IDEA:Development
Okay, I admit I can live without it, but it is a really big thing for me: http://www.jetbrains.net/jira/browse/IDEA-18867
It's annoyed me for ages and I now have over 500 partial incoming changes.
For me it is the bug I just posted: http://www.jetbrains.net/jira/browse/IDEA-20338
If I run Diana 8823 on Mac OS X 10.5.5 I can use it.
If I run a more recent version of Diana (I have not tried all, but 8987 is one I tried) ,
after loading and parsing my project, the CPU goes to 100% and IDEA stops
If this isn't fixed, I'll have no way of using IDEA 8.
Jon Steelman wrote:
IDEA-14591 (http://www.jetbrains.net/jira/browse/IDEA-14591) - really
bugs me every time I write JavaDoc, has a few votes and should be easy
IDEA-17972 (http://www.jetbrains.net/jira/browse/IDEA-17972) - happens
on three machines of our developers and is - well - I don't have words
Yeah this one is odd.
I work next to a guy who is having this problem (Matt Young in the issue)
and I can load the project on my windows box but it dies on his mac. It's
the exact same project. I know he's trying to get more data points on this
"Paul Jakubik" <email@example.com> wrote in message
I don't know if there's an Jira Issue for it at the moment, but my first try with the IntelliJ Database console killed IntelliJ. I only did a 'select * from table' query on a table with 300.000 records, and IntelliJ wanted to render them all, which resulted in 100% CPU time for IntelliJ. I had to manually kill IntelliJ to get my CPU back.
Please file a JIRA issue for this - I don't think we have one already.
"Develop with Pleasure!"
Okay, I just made one here: http://jetbrains.net/jira/browse/IDEA-20364
I don't know how it is for you, but for me this issue seems to have been resolved in (I think) the last version. So I don't see any partial updates anymore, and the incoming view shows really the incoming file. Great work guys!
I spoke to soon. Just after I typed this message, I received partial updates again, and I see the same SVN commit multiple times in the SVN incoming window, but with a 'partial' message next to it. The changed files, timestamp, etc, are all the same: it's just displayed twice.
Edited by: Erik Pragt on Oct 31, 2008 2:53 PM
The long-standing and IDEA-only Alt+Tab problem on Vista (you can't press
Alt+Tab to return to IDEA if there is a dialog open in IDEA).
I saw several people who mentioned this in the forums. Text editor scrolling is really slow in the 8rc1 release (and the last eaps). Pressing PageDown takes 1-2 seconds. Pressing it quickly three times messes up the scrolling text display.
Please vote if you experience the same. It would be great if it could be fixed in the final 8.0 release.
Btw, do you have this property in the config?
Workaround for slow scrolling in JDK6
IntelliJ Labs / JetBrains Inc.
"Develop with pleasure!"
Yes, I do. Sadly that doesn't improve the scrolling. I'm quite sure that it first appeared in one of the last few eaps. See the issue for some more details.
project profiles loose ordering http://jetbrains.net/jira/browse/IDEADEV-29181
Select the desired page size in JdbcConsole options.
The default value is changed from unlimited to 1000.
Erik Pragt wrote:
Clean out the IntelliJ Cache: http://www.jetbrains.net/jira/browse/IDEA-17280
It's easy to get several GB of data cached in IJ and there is no upper limit put on it that I know.
Certainly Browsers can clear ot the cache, why not IntelliJ ?
Stop side-lining problems with maven integration
I'd like to see the following bugs fixed:
for me it's everything VCS (SVN) related - quite frankly, I cannot really trust SVN-integration anymore - doing refactorings across modules with many, many moves feels pretty unsafe for me
and that's just one of the highly visible problems for many people with SVN support in Diana