More exceptions and how to reproduce them

Here are a couple of exceptions which would be nice to have fixed for
5.1 (if there is still time). Some folks might even give one or more of
these high priority.


1. Exception in Inspection Results tool window

There's an exception that still happens in the Inspection Result tool
window, but its JIRA issue has been marked as obsolete:
http://www.jetbrains.net/jira/browse/IDEADEV-2885
http://www.intellij.net/tracker/idea/viewSCR?publicId=60194
http://www.intellij.net/tracker/idea/viewSCR?publicId=60208

To reproduce:
1. Have a source file with some "Declaration access can be weaker" problems
2. "Analyze > Inspect Code..." the source file with at least the
inspection above enabled (it is reproducable with other inspections too,
but not all of them)
3. Right click in the inspection results and "Edit Tool Settings"
4. Click Ok in the dialog.
Result: Exception has happened.



2. Java 5 method used

It seems a piece of the java 5 api is in use again, causing problems for
MacOS people who still run on the ancient jdk 1.4:
http://www.intellij.net/tracker/idea/viewSCR?publicId=60240



3. JSP editing issues

I don't use JSP's myself, but InspectionGadgets' quick fixes and
IntentionPowerPack's intentions run into some problems with JSP files.
Unfortunately the JSP folks don't seem to submit exceptions much, or
seem to avoid these exceptions in some way, because there are hardly are
reports about it in the tracker. However they are trivially easy to
replicate, with for example a built in intention:

<% if (false) { %> // invert if
one
<% } else { %>
two
<% } %>


On the other hand, just release 5.1, cause I want Demetra EAP! :)
Bas

4 comments

Bas Leijdekkers wrote:

1. Exception in Inspection Results tool window


I can confirm this is still happening, and even if no exception occurs after pressing "Ok"
(without changing anything) the inspection results are sometimes cleared ("Nothing left to
show"), which is quite unexpected as well. This happens e.g. with the "@since 1.5" inspection.

3. JSP editing issues
they are trivially easy to
replicate, with for example a built in intention:

<% if (false) { %> // invert if
one
<% } else { %>
two
<% } %>


Hmm, I just tried this in #4137 and it didn't throw an exception, although the result
isn't really correct either:

<% if (!false) { %> // invert if
one
<% } %>
two
<% } else { %>

On the other hand, just release 5.1, cause I want Demetra EAP! :)


Haha, I was thinking the same ;)

Sascha

0

Bas Leijdekkers <leijdekkers@SPAMBLOCK.carp-technologies.nl> wrote:

On the other hand, just release 5.1, cause I want Demetra EAP! :)


Well, hopefully, they'll fix things like
http://www.jetbrains.net/jira/browse/IDEADEV-2675
before 5.1 release.

I am still very unhappy with editor speed on OS X. I realize that I
repeat myself on this topic, but this is my favourite pet peeve.

I do understand that OS X only contributes a little share to the
licenses sold, but editor speed causes a constant frustration for the
user! Konstantin also seems to see that kind of issues, so it's unlikely
that I am day dreaming...

I remember complaining about editor speed for quite some time now. Back
then, I was told to file bug requests. Well, here's one and I am quite
sure, I'll find some more of those for OS X if I'd spent some time
searching the tracker. Virtually no acitvity for about three months does
not encourage me to file more bug requests for these kind of issues!

Virtually every day I get home from work and realize that it's
impossible to develop with pleasure on my system. It might be an OS X
related problem that you can't do anything about it, but then tell us
about it! If it is, I'll start complaining with Apple about it, but
until you do so, the ball is in your court. At the moment, I'd even be
willing to contribute to a paid support incident with Apple if it's
their fault and there is a chance that this will help...

Sorry for those straight words, but that's something that really
concerns me a lot.

Best,

Dirk Dittert

0

Hello Bas,

Here are a couple of exceptions which would be nice to have fixed for
5.1 (if there is still time). Some folks might even give one or more
of these high priority.

1. Exception in Inspection Results tool window

There's an exception that still happens in the Inspection Result tool
window, but its JIRA issue has been marked as obsolete:
http://www.jetbrains.net/jira/browse/IDEADEV-2885
http://www.intellij.net/tracker/idea/viewSCR?publicId=60194
http://www.intellij.net/tracker/idea/viewSCR?publicId=60208

To reproduce:
1. Have a source file with some "Declaration access can be weaker"
problems
2. "Analyze > Inspect Code..." the source file with at least the
inspection above enabled (it is reproducable with other inspections
too,
but not all of them)
3. Right click in the inspection results and "Edit Tool Settings"
4. Click Ok in the dialog.
Result: Exception has happened.


Fixed. Thank you.

2. Java 5 method used

It seems a piece of the java 5 api is in use again, causing problems
for MacOS people who still run on the ancient jdk 1.4:
http://www.intellij.net/tracker/idea/viewSCR?publicId=60240

3. JSP editing issues

I don't use JSP's myself, but InspectionGadgets' quick fixes and
IntentionPowerPack's intentions run into some problems with JSP files.
Unfortunately the JSP folks don't seem to submit exceptions much, or
seem to avoid these exceptions in some way, because there are hardly
are reports about it in the tracker. However they are trivially easy
to replicate, with for example a built in intention:

<% if (false) { %> // invert if
one
<% } else { %>
two
<% } %>
On the other hand, just release 5.1, cause I want Demetra EAP! :) Bas



0

Hi Anna,

Anna Kozlova wrote:

Hello Bas,

>> 1. Exception in Inspection Results tool window


Fixed. Thank you.


Great! Thank you too.

Bas

0

Please sign in to leave a comment.