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.

Bug 235297 - Changing Site Root does not refresh Remote Files
Summary: Changing Site Root does not refresh Remote Files
Alias: None
Product: web
Classification: Unclassified
Component: HTML Editor (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Milutin Kristofic
Depends on:
Reported: 2013-08-30 09:20 UTC by Vladimir Riha
Modified: 2015-05-05 12:28 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Riha 2013-08-30 09:20:02 UTC
To reproduce, please try:
 - create a new Responsive Rabbits demo
 - wait for scanning to finish
 - go to project properties and change site root to public_html/rest
 - confirm

=> Remote Files still shows some files but they are no longer present in Site Root. To fix it, I have to restart IDE

Product Version: NetBeans IDE Dev (Build 201308300001)
Java: 1.7.0_40; Java HotSpot(TM) Client VM 24.0-b55
Runtime: Java(TM) SE Runtime Environment 1.7.0_40-b39
System: Linux version 3.2.0-48-generic-pae running on i386; UTF-8; en_US (nb)
Comment 1 Jan Becicka 2013-08-30 10:03:23 UTC
Close/reopen project should fix it, right? Restarting IDE is not necessary I guess.
Comment 2 Vladimir Riha 2013-08-30 10:05:12 UTC
Nope, closing project does not help in my case
Comment 3 Jan Becicka 2013-08-30 19:00:11 UTC
Cannot reproduce. Adding more asserts.

Changeset: c4024398847d
Author:    Jan Becicka <>
Date:      2013-08-30 20:57
Comment 4 Jan Becicka 2013-08-30 21:10:16 UTC
I accidently closed this bug. Sorry
Comment 5 Tomas Mysik 2013-12-12 06:15:55 UTC
Taking over.
Comment 6 Tomas Mysik 2015-05-05 12:28:10 UTC
This applies also for PHP project.

The problem is in html.editor, in HtmlIndex class. HtmlIndex does not listen on project's classpath (project sources) changes, see the TODO in the Javadoc of the class. BTW perhaps better than removing the HtmlIndex from the cache, the index could stay the same and just its querySupport field could be refreshed. In any case, the index must fire change event if it changes (as it is case when classpath changes).

Once the HtmlIndex is fixed, feel free to reassign back to web/HTML Project component.