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.
Due to this there are some random failures in refactoring tests for TLDs: http://beetle.czech:8080/unittest/Index.jsp?module=extbrowser&module=html&module=db&module=httpserver&module=j2eeserver&module=j2ee&module=j2ee%2Fddapi&module=j2ee%2Fearproject&module=j2ee%2Fejbapi&module=j2ee%2Fejbjarproject&module=j2ee%2Frefactoring&module=schema2beans&module=tomcatint%2Ftomcat5&module=web&module=web%2Fcore&module=web%2Ffreeform&module=web%2Fjspparser&module=web%2Fjspsyntax&module=web%2Fwebapi&module=xml&module=xml%2Fapi&module=xml%2Fcatalog&module=xml%2Fcore&module=xml%2Ftax%2Flib&module=xml%2Ftext-edit&module=xml%2Ftools&module=xml%2Ftree-edit&module=xml%2Fxsl&bQA=true&bUnit=false&testcase=notreportedfails When I look at test run (have to repeat several times, as it passes most of the times), a dialog is opened sometimes saying that the TLD has been modified externally and asks if user wants to reload the file.
This behaves exactly like 55405, but I'm using the correct method you suggested. This is random, but happens very often and in latest builds can be reproduced by hand, therefore I'm raising priority.
The behaviour is caused by changes in CloneableEditorSupport when changes made in FileObject are not synchronized with changes in editor.
Is there anything going on here? This is still blocks refactoring tests. More, I tried it today with on winxp - there's a stackoverflow after refactoring and IDE is locked => raising priority to P1.
Sorry, I didn't notice the blocking issue.
57104 fix helped. However I noticed some problems wit tag handler renaming. See the issue 57368.
v