Highlighting for curved-bracket "( )" for xml documents is not working in NetBeans 6.5 .
It is working in NetBeans 6.1.
This is an example of use the feature:
In NetBens 6.1 I could easy track the parenthesis because the highlighting was working for curved-bracket *( )* .
First integration: http://hg.netbeans.org/main/rev/1b6b0fe452ee. Surprisingly this didn't fix the issue. I'll follow up.
Please stay tuned.
Integrated into 'main-golden', will be available in build *200901110304* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Log: #153670 : Brace matching regression in XML
Verified in trunk
Product Version: NetBeans IDE Dev (Build 20090113163951)
Java: 1.5.0_16; Java HotSpot(TM) Client VM 1.5.0_16-133
System: Mac OS X version 10.5.5 running on i386; MacRoman; en_US (nb)
Updated with status whiteboard.
Integrated into 'main-golden', will be available in build *200901140201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Log: #153670 : call default matcher as a fall through.
The fix will be available as a patch(2). See patch2 plan http://wiki.netbeans.org/NetBeans65Patch2Plan.
was the latest fix re-verified in trunk build? Is the latest fix safe enough to apply in high-resistance fixes branch?
It was verified with 20090113163951. Tony can confirm whether or not the fix was verified in latest trunk build. Ans
yes, it is very safe to apply the fix in high-resistant branch.
The latest added changeset has not been re-verified for Patch2, thus moving to Patch3.
Yes, it was verified in trunk build 20090113163951, and now in latest Build 200901150201. There was discussion of the
safety of this change in email before the change was even made...and it was determined that this was very low risk. Do
we need to include these in evaluations as comments on the issue to get fixes into patches?
It would be a shame to see this not be in patch 2 b/c it was verified in trunk before the cutoff.
I agree, it'll be a shame if this didn't make to patch2. We still have time to re-verify it in patch2. I'm not sure why
it was pushed to patch3.
The fix has been ported into the release65_fixes repository.
It was moved to patch 3 because of the extra change set that was added after the fix was verified. (see desc 7).
Verified in 65patch2.