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 96683

Summary: Is exception already reported?
Product: ide Reporter: Lukas Hasik <lhasik>
Component: Exceptions ReporterAssignee: Jindrich Sedek <jsedek>
Status: RESOLVED WONTFIX    
Severity: blocker CC: blaha, mmirilovic, pzajac
Priority: P1    
Version: 5.x   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter:

Description Lukas Hasik 2007-02-27 13:24:29 UTC
It could be useful to check if the reported exception haven't been already
reported in Issuezilla. The check hasn't be too smart. IMO, it's enought to find
first line with substring "netbeans" in the exception and look for all issues
that  contain the line in attachment or description. 

This feature should be called only on demand. It can be issuezilla's resources
consuming operation. It cannot be automated because somebody has to evaluate if
reported and founded exceptions are similar/same...

You can use following URL to query issuezilla. replace LINE with particular
exception line. Be careful that the line can't contain spaces.

http://www.netbeans.org/issues/buglist.cgi?version=6.0&field0-0-0=attachments.thedata&type0-0-0=substring&value0-0-0=LINE&field0-0-1=longdesc&type0-0-1=substring&value0-0-1=LINE
Comment 1 Petr Blaha 2007-02-27 15:26:32 UTC
This would help us to reduce the number of open reports and these issues should
be resolved asap.
Comment 2 pzajac 2007-02-27 15:59:37 UTC
Good idea. It's not 100% reliable. Imagine:

IllegalStatedException("File was not normalized") 
at org.openide.fs.FileUtil.to(String) ...
at org.netbeans.modules.j2ee.blabbla

If you try query on org.openide.fs.FileUtil.to you can found a lot of 
incorrect duplicates. 

You need to ask for  
at org.netbeans.modules.j2ee.blabbla

There should be implemented selection of line for query.
Comment 3 Jindrich Sedek 2007-04-12 15:56:31 UTC
We are not going to fix this issue, because it takes too long time and it blocks
issuezilla to execute such a query.