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.
Product Version = NetBeans IDE 7.4 (Build 201310111528) Operating System = Linux version 3.5.0-37-generic running on amd64 Java; VM; Vendor = 1.7.0_25 Runtime = Java HotSpot(TM) 64-Bit Server VM 23.25-b01 Many times (let's say 80% of the time) when a file is deleted from within the project tree (Window->Projects) the project tree is collapsed to "Source Files" - I mean the "Source Files" remains expanded but all the sub-folders are collapsed. This is really inconvenient as I have to expand all the tree and subtrees again and again... And even more inconvenient if after this "bug" I need to delete other file(s) and it happens again.
This happens quite often even if I do a commit or update to/from SVN, either of full project tree or only of a sub-tree... From my point of view, NetBeans 7.4 is in many cases worse product than was 7.3.1 and though 7.3.1 tends to freeze completely from time-to-time, it is not so often as bugs occure in 7.4.
I cannot reproduce with a java project under SVN in the Projects view at all. I tried updating, deleting files and packages but the tree was not collapsed even once. Please provide exact steps to reproduce, or best make a screencast demonstrating the problem.
I am able to reproduce this in the Files view though. What project type are you using? Regarding the Files view: 1) i found some problems on the versioning side, will look into it 2) PhysicalView.VisibilityQueryDataFilter is context-less and fires events that result in complete refresh of all nodes, should react only to relevant events
OK, I did notice that this tree collapses (in PROJECT window tree, not Files window - I do not use it so cannot tell) when I do an UPDATE from SVN and some file/folder was renamed/removed (renaming is done by removing the old file and adding it with a new name). If the tree is expanded in the node (folder) where this rename/remove happened after the UPDATE the whole project window tree is collapsed. This even happens sometimes if I only rename/remove some file on my own (before the COMMIT could be performed). Working on Ubuntu - cannot tell whether the same happens on Windows machine. NB 7.4 build 201310111528.
(In reply to shadyyx from comment #4) Forgot to mention I'm working with Zend Framework 2 PHP project (containing lot of JS frameworks and libraries for frontend, such as jQuery, Bootstrap, CoffeeScript, Backbone, Handlebars, Underscore, etc.).
making some improvements in versioning visibility handling: core-main #68b837ccad39 and core-main #68b837ccad39 - for 1.7 and newer working copies it makes no sense to handle the visibility because since 1.7 subversion removes deleted/renamed folders immediately. For 1.6 checkouts - well, users will have to upgrade to a newer metadata format. passing to projects: it should handle Comment #3, point 2. For SVN 1.6 and older and e.g. for CVS it still works poorly. reporter: what working copy format are you using?
Not sure, I think it's SVN 1.6 with .svn folder in every subfolder. Sadly I cannot upgrade to SVN 1.7 as I am part of a bigger deploy environment (with many projects and hundreds of developers) where the SVN upgrade is not possible...
> Sadly I cannot upgrade to SVN 1.7 as I am part of a bigger deploy environment (with many projects and hundreds of developers) where the SVN upgrade is not possible... It should not matter what version you have on the client side. You can have a server where svn 1.6 is running and still have a local checkout in 1.7 version. That is unless you somehow share your working copy (you should not, but i've seen those too) or you have not admin privileges for your local machine.
After upgrading the SVN working copy to 1.7 the issue no longer exists. Though this cannot be considered as a fix, there is a working solution, thus closing the bug.