Develop with 7.0 Pleasure: bugs that still hurt

With IDEA 7 reaching RC status, what bugs (not feature requests) are still present in 7.0 that bring you pain and you want to beseech JetBrains to address before 7.0 is released? Our goal here is to highlight bugs that we would hate to have masses of non-EAP users suffer through once 7.0 gets release. Good luck!

Please provide a link to the issue in question or create the issue if it isn't already in JIRA. FYI - To create an issue, go here & select IDEA feedback:
http://www.jetbrains.net/jira/secure/CreateIssue!default.jspa

17 comments
Comment actions Permalink

Inspections are IDEAs bread & butter, and the current UI to get the 'detailed'
error description is an excercise is accurate mouse clicking.
http://www.jetbrains.net/jira/browse/IDEA-13997


0
Comment actions Permalink

Code coverage display has not been working for me since build 7269:

http://www.jetbrains.net/jira/browse/IDEA-14811

I continue to get this exception when I try to view code coverage:

Could not initialize class com.vladium.logging.Logger
java.lang.NoClassDefFoundError: Could not initialize class com.vladium.logging.Logger
at com.vladium.emma.data.DataFactory.mergeload(DataFactory.java:327)
at com.vladium.emma.data.DataFactory.load(DataFactory.java:56)
at com.intellij.coverage.CoverageSuiteImpl.b(CoverageSuiteImpl.java:15)
at com.intellij.coverage.CoverageSuiteImpl.getCoverageData(CoverageSuiteImpl.java:9)
at com.intellij.coverage.SrcFileAnnotator.showCoverageInformation(SrcFileAnnotator.java:65)
at com.intellij.coverage.CoverageDataManagerImpl.a(CoverageDataManagerImpl.java:120)
at com.intellij.coverage.CoverageDataManagerImpl.access$700(CoverageDataManagerImpl.java:43)
at com.intellij.coverage.CoverageDataManagerImpl$4$1.run(CoverageDataManagerImpl.java:1)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.run(LaterInvocator.java:22)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
at com.intellij.ide.IdeEventQueue.c(IdeEventQueue.java:161)
at com.intellij.ide.IdeEventQueue.b(IdeEventQueue.java:106)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:43)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)

0
Comment actions Permalink

These two must be a Linux user's worst nightmare:

"Class to import", doesn't put the focus on the popup "class to import" window: http://www.jetbrains.net/jira/browse/IDEA-14647
IntelliJ ignores keyboard on Linux after Alt-Ins: http://www.jetbrains.net/jira/browse/IDEA-15434

0
Comment actions Permalink

Installation issues:

My system: a Vista Home Premium box upgraded from Windows Media Center.

1. Installing for just the selected user instead puts a launch icon on all user's desktops.
2. WORST - build #7323 does not launch from the desktop shortcut. This is an on going problem for many builds throughout the summer.

0
Comment actions Permalink

If it is useful, in regard to the desktop icon not launching, I tried running idea.exe directly from the bin directory using Cygwin to drive my command line. The output:

Brian@EROS /C/Program Files/JetBrains/IntelliJ IDEA 7323/bin
$ ./idea.exe
Using JVMTI (1.6.0_02-b06;Sun Microsystems Inc.;mixed mode, sharing;Windows;32 bit JVM)
Error occurred during initialization of VM
java/lang/ClassNotFoundException: error in opening JAR file ..\lib\boot.jar

Brian@EROS /C/Program Files/JetBrains/IntelliJ IDEA 7323/bin
$ dir ../lib/boot.jar
../lib/boot.jar*

0
Comment actions Permalink

no JIRA issue == no cigar :)


0
Comment actions Permalink

This one is marked as FIXED but it's back in RC2: http://www.jetbrains.net/jira/browse/IDEADEV-21026

0
Comment actions Permalink

These are the most hurting bugs for me, which I want to see fixed in Selena
release:

Good code yellow: private field marked as unused:
http://www.jetbrains.net/jira/browse/IDEA-15361

Replace Duplicates does not detect simple duplicates:
http://www.jetbrains.net/jira/browse/IDEA-15320

Debugger's auto-mode:
http://www.jetbrains.net/jira/browse/IDEA-13666
http://www.jetbrains.net/jira/browse/IDEA-12942
http://www.jetbrains.net/jira/browse/IDEA-12940

0
Comment actions Permalink

now that you mention it, you're right. i never considered clicking on the details-link difficult, but maybe that's because i'm quite good at first person shooters...

+1

0
Comment actions Permalink

IDEA-15447 for the launch issue.

(Left out the link first time.)

http://www.jetbrains.net/jira/browse/IDEA-15447

Message was edited by:
B. K. Oxley (binkley)

0
Comment actions Permalink

There are a host of unresolved Glassfish issues that make using Glassfish very painful.

http://www.jetbrains.net/jira/browse/JEEAS-143

http://www.jetbrains.net/jira/browse/IDEADEV-14176

Also, hitting stop in the server dialog closes the server dialog, but does not stop the local server instance. I tried to create an entry in jira, but jira kept telling me that I did not select a valid project (intellij feedback or jee servers).

0
Comment actions Permalink

There are a load of issues which I really need to put into Jira, but haven't had time to do. They revolve mainly around the following two areas:

1) There are a raft of Hibernate mapping file validation issues - my mapping files are more red than not currently. The major problems seem to resolve around the resolution of Hibernate components, or when the mapping files exist in JAR files in the classpath, rather than being in the source root. Resolution of mapped fields seems a bit off with complex object hierarchies as well.

2) JavaScript editing from version 72xx upwards has proved troublesome, due to wierd behaviour by the editor. Simple things like CTRL-W selection being inconsistent and wrapping sections of code using CTRL-ALT-T adding loads of whitespace, nothing major.

I'll attempt to file them all into Jira tomorrow.

0
Comment actions Permalink

I have exactly the same problem with Tomcat, but as mentioned in my other post I've been a bit remiss in raising Jiras....

0
Comment actions Permalink

http://www.jetbrains.net/jira/browse/IDEA-13500
This is nasty if you don't know about it, committing an SVN rename often
forgets to delete the old class which means you get compile errors if it
is imported with wildcard imports.
There's an easy workaround once you're aware of it (refresh the
changelist), but it means you have to think very carefully before you
check in any file rename operations.
R

0
Comment actions Permalink

And again in build #7330 (RC3) --

Brian@EROS /C/Program Files/JetBrains/IntelliJ IDEA 7330/bin
$ ./idea.exe
Using JVMTI (1.6.0_02-b06;Sun Microsystems Inc.;mixed mode, sharing;Windows;32 bit JVM)
Error occurred during initialization of VM
java/lang/ClassNotFoundException: error in opening JAR file c:\progra1\jetbra1\intell~2\bin\..\lib\boot.jar

Brian@EROS /C/Program Files/JetBrains/IntelliJ IDEA 7330/bin
$ dir ../lib/boot.jar
../lib/boot.jar*

0
Comment actions Permalink

For the Mac users:

If the navigation bar is permanently visible (View > Navigation Bar) the
close button looks very ugly on the Mac:
http://www.jetbrains.net/jira/browse/IDEA-13619

When using the Quaqua look and feel an exception happens on every
project open which prevent the editors from showing (
http://www.jetbrains.net/jira/browse/IDEADEV-21309 ). This is an
exception inside quaqua and it is fixed since Quaqua version 3.7. IDEA
still includes version 3.6.6 however. It would be great if a newer
version of Quaqua could be included:
http://www.jetbrains.net/jira/browse/IDEA-15578


Bas

0
Comment actions Permalink

These bugs still seem to be present in IDEA 7.0.

0

Please sign in to leave a comment.