NB 4.2 2005 05xx.
JDK 1.5.0 building for JDK1.4

I have tried three daily builds since the start of May, and all of them have 
JSP Debugger defects. I realise my previous complaints about JSP debugger some 
of which were due to my using project dirs and nb configs from previous 
releases. However, this time after four weeks of trials & tribulations, I 
believe the NB4.2 JSP Debugger released for all of May is defective. The last 
working debugger for NB4.2 is an April release.
I have cleaned and reconstructed my projects and NB configs. The only configs 
I reused from my April nb4.2 are my platform, library and editor indentation.

These are the aberrant behaviour:
1.
Cannot mark a new debug breakpoint or toggle current breakpoint after debugger 
has started.

2.
Cannot run to cursor.

3.
Sometimes will not run to breakpoints marked in an included JSP.

4.
Keeps on getting stalled in class libraries where there had been no 
breakpoints. It is not apparent that it is stalled at some class library until 
I click [pause debug]. Had to click proceed a few times, after which it 
ignores all breakpoints and carry JSP to completion - making the break points 
pointless.

5.
If it is not stalling, it may visibly pause at a class library for no apparent 
reason.

6.
Or it may pause at the start of an included JSP which has breakpoints. It 
pauses at the first line not at the breakpoints of the JSP.

7.
I stopped and restarted the debugger without stopping the Tomcat instance.
This solves the stalling at class libraries, but all other defects still 
evident. So far I am limping along to debug my projects using this kluge. The 
only debug flow button usable is [skip over]. On the other hand, I might 
regress to using April's release.

7a.
After using this kluge a few times, when I exit NB, a dialog pops up to inform 
me there is a series of debug sessions still active. I cancel to look around. 
No, can't find any active debug sessions. Where? Anyway, I exit NB regardless 
(or some people prefer saying irregardless) of the unlocatable multiple active 
debug sessions.

7b.
Using this kluge, an error pop-up constantly appears at every [skip over] 
click, which complains of some channel closed.

I should be able to attach some exception dumps tomorrow.
Also, I am debugging a multiple-context application.
I'll try if I have time to create and debug throug a clean single context app.