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 47425 - [gjast] Debug messages in console "dropped error: error: "
Summary: [gjast] Debug messages in console "dropped error: error: "
Status: CLOSED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: _ tball
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-18 22:43 UTC by Marian Mirilovic
Modified: 2007-09-26 09:14 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 2004-08-18 22:43:44 UTC
[nb beta1](200408181510), [jdk1.5.0](b63)

- last Beta 1 contains (my manager told us) fixes
for issues 46611 and issue 46991

Steps to reproduce:
- run IDE
- create new Java Application Project
- write to the main method :
     new X()
- and wait until it's underscored in the editor
-> to the console are logged messages like :

dropped error: error: Main.java:24,12:
<identifier> expected
dropped error: error: Main.java:25,5: '(' or '['
expected

each time you write not compilable code to editor
and wait for underscore these messages are logged
Comment 1 Martin Matula 2004-08-18 22:59:51 UTC
This is reproducible also in the main trunk.
Does this issue mean that the messages should be eliminated? Should
the fix be integrated also to the beta 1 branch?
Comment 2 Marian Mirilovic 2004-08-18 23:05:24 UTC
I think this fix must be integrated to the beta 1 , 
... but wait a morning ...

Honza, what do you think ?
Comment 3 Jan Chalupa 2004-08-18 23:08:55 UTC
Well, they should have been eliminated, but it's already too late for
beta 1. I'm afraid we'll have to live with them for now. :-(
Comment 4 Martin Matula 2004-08-18 23:28:53 UTC
This messages seems to be quite rare (not as before when all the
parser errors in the file seem to be printed to the console). In fact
I have never noticed these in the console before. So I don't think
they are beta blockers.
Comment 5 Martin Matula 2004-08-18 23:43:59 UTC
Hm. OK, I see the messages are displayed quite often. And I also found
out that it is not reproducible in trunk (I had a build with the gjast
from beta-1 branch). So it seems that these messages were eliminated
with one of the later commits to gjast:

revision 1.61
date: 2004/08/16 23:58:49;  author: tball;  state: Exp;  lines: +1340
-1370
Shared name tables between compilations, to improve performance and reduce
GC a little.
----------------------------
revision 1.60
date: 2004/08/12 22:45:26;  author: tball;  state: Exp;  lines: +1943
-1918
Implemented ClassReader jar file sharing.  Performance gain is only
20-30%,
but since much less garbage is generated there aren't as many GC lags as
before.
----------------------------
revision 1.59
date: 2004/08/11 19:31:29;  author: tball;  state: Exp;  lines: +360 -366
46990: fixed lastToken values for annotations without default values.
----------------------------

Since this issue does not need to be integrated to beta-1 branch I am
closing it.
Comment 6 Marian Mirilovic 2004-08-24 19:24:00 UTC
verified in [nb_dev](200408231800]
Comment 7 Quality Engineering 2007-09-20 12:46:11 UTC
Reorganization of java component