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 184243 - [69cat] Poor scanning of projects, lingering error annotations
Summary: [69cat] Poor scanning of projects, lingering error annotations
Status: RESOLVED INCOMPLETE
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 normal with 1 vote (vote)
Assignee: Jan Lahoda
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-15 09:27 UTC by _ hair
Modified: 2012-10-22 14:38 UTC (History)
0 users

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 _ hair 2010-04-15 09:27:12 UTC
[ BUILD # : 49ed57cba68e ]
[ JDK VERSION : 1.6.* ]

Upon opening netbeans many of my projects (all submodules from a maven project)
are annotated with errors.


WORKAROUND: If i open a red annotated java file in the editor and go to the
error line containing the supposed compilation failure, then click on the "Go
to source" the associated java file opens. This java file is also from one of
my already open projects in netbeans.
After netbeans has opened this new file in the editor, and the "Scanning
projects" task quickly runs, the original file opened "turns to green" (the red
error annotation disappears).

This is evident, to me at least, that netbeans is failing to scan projects
correctly at startup (or switching "Project Group").

This may be related to #184233 ... i don't know... at least they present
different use cases so i've entered different issues...
Comment 1 Jan Lahoda 2010-04-15 20:17:58 UTC
Could you please start the IDE with:
-J-Dorg.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.level=FINE
command line flag, ideally with a clean userdir and open your projects and then perform the workaround on a file and attach resulting ${userdir}/var/log/messages.log (possibly also backup the messages.log before performing the workaround so that we can see the difference, note that the logs are flushed with certain delay ~5s). Thanks.
Comment 2 _ hair 2010-04-20 15:46:33 UTC
i had some log output yesterday... but it's taken me so long to log into bugzilla :-(
Comment 3 Marian Mirilovic 2012-10-22 14:38:36 UTC
Without requested information for >2 years, closing