dev build 200109110100
IBM JDK 1.3
- I hit F9 to compile a file in the editor. When errors are found they should up in the output window so I double-click on them.
- Instead of jumping to the line number in the file which is already open, the editor opens up a second (sometimes a third) window of the same file and jumps to the
line number there.
- The editor should use the window which is already open
- I'm in MDI mode
Confirmed on my Solaris too in build #20010914-containing terminal
Changing Platform and OS. Also increassing priority to P1 (If do not
agree, please change).
It is 100% regression and should be fixed into the beta.
Note, that I verified it with only one mounted filesystem (sampledir),
so this isn't the case when the source is mounted more than once!
OK, changing owner.
It works for me as well as for Jan Zajicek. Please, describe steps how
to reproduce this problem.
Ok, It's true that I cannot reproduce it now. But is also true that I
was able to reproduce it before I have restarted the ide
(build#20010914). Now it is hard to say what could cause such
behaviour. I will keep an eye on it ;-) So sorry for wide distrurb. Honza.
This is 100% reproducible on my end.
1) Take dev build 200109110100
2) Open a source files by double-clicking on it from the explorer
3) Cause some sort of error in the source-code and hit F9 to compile
4) Netbeans will open a second instance of the file (even though one
is already open) and jump to the line containing the error
Created attachment 2579 [details]
patch file - put into lib/patches
I still cannot reproduce it. I made some changes into a related code
last week - can you try whether the attached patch makes it working
Gili, do you see the behaviour in the latest builds? If so, does the
patch solve the problem? Thanks.
dev build 3.3 20010919
IBM JDK 1.3
After clicking on the error in the output window I get an NPE.
Created attachment 2605 [details]
Seems like the issue is fixed in dev build 20010919
but I'm not sure because the output window looks
completely different and acts weird ;) Personally I
preferred the old look..
Anyway, I guess this is fixed..
Ok, I am closing it as not reproducible.
Issue is back in dev build 200109280100
I still cannot reproduce it :-(. Gilli, have you tried the patch? Any
The patch doesn't work. I've included ide.log for
your review. No exceptions are thrown when I
double-click on the error in the output window, but
there are a few thrown before it. You will notice
the last line in the log is me trying to compile
Created attachment 2773 [details]
Also, when you try to repro this issue, please make
sure you're using a fresh userDir and try IBM JDK
1.3, not Sun's.
We have resolved a similar bug caused by old xerxces.jar in IBM's JDK
distribution. Is this one still valid?
As I explained to you, OS/2's distribution doesn't
come with XERCES.JAR at all so your explanation
doesn't work for this bug. Something else is the
cause or this is the result of multiple issues. So
yes, this is still a valid issue.
I'm unable to repro it under dev build 200110040910
but since I had no problem reproing under
200109280100 (6 days beforehand) I recommend we
leave this issue open under REMIND so we can check
if it's still around a month from now.
please reopen if it isn't gone.
moving terminal emulator issues to terminalemulator component.
To see the correct version and target milestone of this issue look at Issue