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 6.9 (Build 201006101454) Operating System = Windows Vista version 6.0 running on x86 Java; VM; Vendor = 1.6.0_20 Runtime = Java HotSpot(TM) Client VM 16.3-b01 I've tested NetBeans 5.8 and 5.9 on different machines, and in all cases, when committing a large project in 5.8, the list of files to commit comes up very quickly, near instant. In NetBeans 5.9, I see the "Preparing Commit..." progress bar and wait anywhere between 8-12 seconds before I can choose which files to commit and then hit the commit button. Was something major changes, was caching disabled in 5.9? I find it very odd that this huge of a performance hit was not noted in testing. It would be great if this could be fixed, or if caching could be introduced to speed up the process.
You are right, the preparations for a commit now takes bit (or much on large projects) longer. But *only* when you commit from the Project/Files/Favorites views. In that case cached information (file statuses) is not used and selected context is scanned before the commit can be invoked. Why did we decide to change the behavior? Well, some users used to modify files externally (added new files, modified, deleted them etc.) then immediately ran a commit and complained because the IDE missed some of those files in the commit table. I agree that this may be inconvenient for other users (like you), that's why there are two options to bypass this preparation process. 1) Either commit from the Versioning view (Subversion -> Show changes) or the Diff view (Subversion -> Diff). When you commit from these views, the preparation process will be skipped since we assume that status of all files is known already. 2) Or disable the process completely by running the IDE with the commandline switch: -J-Dnetbeans.subversion.commit.deepStatusRefresh=false Sorry, we do not intend to change it back, but i hope that the two suggestions will suit your needs.
I would like to have an option to disable this in the preferences instead of a startup switch. It's very annoying to wait 3-5 minutes (no kidding) to commit. With a large PHP project it can take very long. Regards, Merijn
bump up netbeans 7.3 alpha from 13march 2013 and all previous days after days my project was growing bigger and bigger, and with it - waiting to make commits, now i finally started looking for a solution, and thank god i found it quickly:). Option to switch from one behaviour to the other one should be in configuration or under right click to choose from - do commit with or without scan. Regards Silvestris
...I wonder how many people were complaining about old behaviour so you have to change defaults (instead of giving option to them)... (and if you ask: I always commit from project view)
This problem still exist with netbeans 8.2 and jdk 1.8.0_65
Same as in https://netbeans.org/bugzilla/show_bug.cgi?id=209126#c7 Please do not reopen that old issues, file a new one, attach the full messages log and a profiler snapshot there demonstrating the commit. Thanks. http://wiki.netbeans.org/FaqLogMessagesFile http://wiki.netbeans.org/FaqProfileMeNow