This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 96536 - Report doesn't contain exception stack trace
Summary: Report doesn't contain exception stack trace
Status: CLOSED FIXED
Alias: None
Product: ide
Classification: Unclassified
Component: Exceptions Reporter (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Jan Horvath
URL:
Keywords:
: 96058 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-02-26 08:21 UTC by Marian Mirilovic
Modified: 2007-04-02 13:41 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Mirilovic 2007-02-26 08:21:59 UTC
see issue 96534
Comment 1 Jindrich Sedek 2007-02-26 10:59:16 UTC
There is a link to anna.nbextras.org where you can find a stack trace, why to
copy it again? It's the same as an attachment.
Comment 2 Marian Mirilovic 2007-02-26 11:04:21 UTC
I would prefer all informations in one system , BTW I saw somebody are copying
exceptions into description area, so why don't do it automatically ?
Comment 3 Jindrich Sedek 2007-02-26 11:13:50 UTC
We can do this automatically it's an easy thing but what is the difference
between a link to different system and link to attachment? I don't want to paste
a stack trace into description, because when filling an issue there is always a
message "You will have an opportunity to add attachments after this issue is
created; please do not paste large amounts of text into the description." I
expect there is some reason for this message !

http://www.netbeans.org/issues/enter_bug.cgi?component=logger

Comment 4 Petr Blaha 2007-02-26 11:18:42 UTC
We plan to print several lines from stack trace in IZ comment. I guess that this
one could resolve this issue, see issue #96058. These lines could be used for
searching appropriate stack trace in open IZ issues.
Comment 5 Marian Mirilovic 2007-02-26 11:32:48 UTC
As I said, now we are not able to search for the stack-trace in IZ and that's
wrong. Please attach at least first few lines (or important ones if you know
which one are important), current information from anna.nbextras.org is not enough.
Comment 6 Petr Blaha 2007-02-26 11:35:30 UTC
Marian, is this issue a duplicate of issue #96058?
Comment 7 Marian Mirilovic 2007-02-26 11:41:14 UTC
agree with Petr Blaha, there are few reasons to have the stack-trace in IZ :

- ability to search for duplicates (I don't think all newly reported issues will
come through anna, do you ?) P1 imho

- hold all important informations in one system 

- it's a little bit annoying if you get issue "NullPointerException' after a
while you open an IZ page and there is information like ".... look at " , so you
need to go to another system and look there for additional informations
Comment 8 Marian Mirilovic 2007-02-26 11:42:39 UTC
*** Issue 96058 has been marked as a duplicate of this issue. ***
Comment 9 Marian Mirilovic 2007-02-26 11:46:01 UTC
> Marian, is this issue a duplicate of issue #96058?
Yes, or vice-versa ... prefer the whole stack-trace in attachment of course (see
issue 96537 )
Comment 10 Jan Horvath 2007-03-21 15:35:54 UTC
fixed. first 10 lines of stacktrace are added to the description.

Checking in IssuezillaHandler.java;
/cvs/logger/StrutsExceptions/src/java/org/netbeans/modules/exceptions/web/IssuezillaHandler.java,v
 <--  IssuezillaHandler.java
new revision: 1.5; previous revision: 1.4
done
RCS file:
/cvs/logger/StrutsExceptions/src/java/org/netbeans/modules/exceptions/web/Utils.java,v
done
Checking in Utils.java;
/cvs/logger/StrutsExceptions/src/java/org/netbeans/modules/exceptions/web/Utils.java,v
 <--  Utils.java
initial revision: 1.1
Comment 11 Marian Mirilovic 2007-04-02 13:41:41 UTC
Hope this is just temporary - I still prefer the whole stack-trace as attachment.