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 8.1 RC2 (Build 201510122201) Operating System = Windows 7 version 6.1 running on amd64 Java; VM; Vendor = 1.8.0_60-ea Runtime = Java HotSpot(TM) 64-Bit Server VM 25.60-b23 Reproducibility: Happens every time You must work against active SVN repository. --Use Case-- 1. Put several breakpoints in the source file (Java in my case) 2. Modify the file and commit changes --Additional Info-- It does not matter whether the commit has been made within or from outside the IDE. --Actual Result-- Just after the commit, once IDE refreshes the source, all breakpoints are gone. Moreover one new breakpoint appears, always at the first line. --Expected Result-- It is clear that breakpoints should not be removed
Created attachment 156739 [details] Auto-breakpoint
Created attachment 156742 [details] Video showing that SVN > Commit does nothing with breakpoints. Product Version: NetBeans IDE 8.1 RC2 (Build 201510122201) Java: 1.8.0_60; Java HotSpot(TM) 64-Bit Server VM 25.60-b23 Runtime: Java(TM) SE Runtime Environment 1.8.0_60-b27 System: Linux version 3.13.0-37-generic running on amd64; UTF-8; cs_CZ (nb) I cannot reproduce it.
--Additional Information-- - removed breakpoints are still displayed in the Breakpoints view - new breakpoint (at 1st line) is not displayed in the Breakpoints view - removed breakpoints are again correctly displayed in the editor after the IDE restart - new breakpoint (at 1st line) does not exist longer after the IDE restart
Thanks. I was able to reproduce it via using $Revision$ and/or $Date$ strings in the versioned fie. To activate the keyword expansion, one need to run: svn propedit svn:keywords <file name> and set: Revision Date as the content on commit. Then after the next commit the keywords in strings are expanded, file is refreshed and just one breakpoint at line 1 is visible. However, as you said, breakpoints retain their original line numbers, therefore subsequent Debug action suspends correctly on them and re-paints the annotations at correct lines. Also restart or simply closing and re-opening the file corrects the annotations as well. Due to this reason we agreed with Jiri that this is not a showstopper for 8.1 and that P3 is a more appropriate priority. We'll be fixing this into the next NB version.