Hard to reproduce.
1. Create new Web Application project
2. Add new servlet
3. Deploy application to glassfish server
4. enter into debug mode
5. execute application in debug mode
6. set breakpoint within servlet
7. sometimes breakpoints are not shown at the left side-bar
Created attachment 51557 [details]
image showing that breakpoint are not properly shown within editor
Any idea when? Does closing and reopening the file help? Scrolling outside of the visible area and back? Resetting the
breakpoint? Did you see any exceptions? Could you please attach <userdir>/var/log/messages.log file? Thanks a lot
I've had the same problem in a non-web Java application running Netbeans 6.0-RC1. The line was not highlighted in the
editor. Restarting the IDE everything was alright.
It happened again after working for a while. Closing and reopening the file was not enough to restore the breakoints in
moving opened issues from TM <= 6.1 to TM=Dev
Kelahcim, Aldobrucale are you still experiencing this problem? Please could you attach the messages.log?
And Aldobrucale, in your case - have you observed this on Linux as well?
Product Version: NetBeans IDE 6.1 RC2 (Build 200804170002)
Java: 1.6.0_10-beta; Java HotSpot(TM) Client VM 11.0-b11
System: Windows XP version 5.1 running on x86; Cp1250; cs_CZ (nb)
Well, it just happened to me as well. Although I created several breakpoints, they were not visible in the editor.
And the steps to reproduce are incredibly simple!
1, Create new java project (e.g. javaaplication1)
2, Create a new package (e.g. javaaplication1.logic)
3, drag&drop Main.java into this package (refactoring should run)
and thats it. Try to create a breakpoint now.
I was able to reproduce this couple of times, always with a new usedir. Jirka V. tested this right now with the same result.
I am affraid this is P1
Created attachment 60698 [details]
The debugging works correctly, only the breakpoints are only not visible in the gutter. They are added to breakpoint
list and debugger stops on them normally.
This affect only breakpoints, other annotations are ok.
AnnotationProvider.annotate() is not called for renamed file. Since the lookup contains not only FileObject, but also
DataObject, I guess that the client is responsible for listening on DataObject.PROP_PRIMARY_FILE to get the new FileObject.
Moving to debuggerjpda where we implement AnnotationProvider.
Fixed in trunk:
Integrated into 'main-golden', available in NB_Trunk_Production #159 build
Log: #119879 - When annotating, listen on the changes of DataObject's primary file.
This is necessary to annotate renamed files.
Yes, I can reproduce it with nb 6.1 RC2 under ubuntu. I'm attaching the message log, in case you still need it.
Created attachment 60748 [details]
I did not find anything unusual in your message.log file, but thanks anyway. The problem is fixed in trunk (post-6.1
I've transplanted the changeset http://hg.netbeans.org/main/rev/15fab9719250 from main repository into release61_fixes
repository as http://hg.netbeans.org/release61_fixes/rev/bde0c7a68536
date: Sat Apr 26 11:26:43 2008 +0200
summary: #119879 - When annotating, listen on the changes of DataObject's primary file.
Verified with patch2.