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.
Product Version = NetBeans IDE Dev (Build 040217) Operating System = Linux version 2.4.20-18.9 running on i386 Java; VM; Vendor = 1.5.0-beta2; Java HotSpot(TM) Client VM 1.5.0-beta2-b38; Sun Microsystems Inc. Java Home = /usr/local/java/j2sdk1.5.0/jre System Locale; Encod. = cs_CZ; ISO-8859-2 Home Dir; Current Dir = /usr/local/home/delphym; /usr/local/forte/forte3/NBdev-last/netbeans/bin IDE Install; User Dir = /usr/local/home/delphym/NBdev-last; /usr/local/home/delphym/.netbeans/dev ------------------------------------------------------------------------------- I've performed cvs-> log, status, annotate, diff on cvs files and exit the ide (didn't closed cvs outputs in Editor) and find lots of various E. in ide.log which I'm attaching I hope it's not serrious and that only thos E are printed, thus leaving as P3. Agree?
Created attachment 13471 [details] ide.log full of IOE and others E. becasue of vcs visualicers
The problem is caused by OutputVisualizer$OutputTopComponent. However, I'm not able to reproduce it. The TopComponent defines getPersisteceType() = PERSISTENCE_NEVER. Isn't this a problem in core/windows/persistence ? Moving to core/windows for evaluation.
I'd like to mention that I'm using my own build build today at c. noon also I'm running it on JDK beta 1.5
Dan, it's time to use keywords !
Marian, I know that. But I don't think this bug is 100% related to jdk1.5 thus I didn't used the keyword now. And won't plan to use it if I'm not sure it's caused by using 1.5. Instead of that I'm always adding Milan Kubec to CC' becasue he like to be informed about such unsure cases and it's up to him to determine to use proper kw. thanks for understanding
Thanks, for adding me on cc. This issues could be related to JDK 1.5.0.
re-evaluate please ...
Imho, In current dev builds problem disappeared. But 4.0 is totally different then 3.6
Dan, is it reproducible in current trunk ?
Works for me too. It's probable that Tim's rewrite of output window solved this bug. I'm closing as fixed, please reopen if reappears. Thx.
ok