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.
After an SVN commit, the left sidebar coloring for the changed/removed/added lines in a file does not update. It updates only after closing and reopening the file in the editor. Furthermore, the blue color of the filename in the tab does not change back to black until the editor is restarted.
Could you please attach your messages.log file and reopen ? Thanks in advance. http://wiki.netbeans.org/FaqLogMessagesFile
Created attachment 137773 [details] messages log file
I had the wrong NB version - it's 7.3.1, not 7.4.
Is it reproducible for every file? > Furthermore, the blue color of the filename in the tab does not change back to > black until the editor is restarted. Does it change in the Projects/Files view? Please run with -J-Dorg.netbeans.modules.versioning.ui.diff.DiffSidebarManager.level=-1 and -J-Dorg.netbeans.modules.subversion.ui.commit.CommitAction.level=-1, try a commit and attach the messages.log after a while when the status does not change.
reopen when you provide the requested information, thanks.
(In reply to comment #4) > Is it reproducible for every file? > > Furthermore, the blue color of the filename in the tab does not change back to > > black until the editor is restarted. > Does it change in the Projects/Files view? > > Please run with > -J-Dorg.netbeans.modules.versioning.ui.diff.DiffSidebarManager.level=-1 and > -J-Dorg.netbeans.modules.subversion.ui.commit.CommitAction.level=-1, try a > commit and attach the messages.log after a while when the status does not > change. No, the color remains blue in the Projects and Files views, even after closing and reopening the file.
Created attachment 137842 [details] messages log file Ran NB with -J-Dorg.netbeans.modules.versioning.ui.diff.DiffSidebarManager.level=-1 -J-Dorg.netbeans.modules.subversion.ui.commit.CommitAction.level=-1 options set in netbeans.conf.
See comments and new attachment below.
There is absolutely no trace of any commit-related log message in the log. Did you try to commit as i asked? Otherwise the log is useless. Anyway, again, does it happen for all files? If you run Subversion -> Show Changes action, what status displayed for the file? Can you also try to: 1) make some modification in a file -> the file should turn blue and the diff sidebar in editor should show the modification, right? 2) run Subversion -> Revert Modifications -> everything should turn to uptodate again, right?
(In reply to comment #9) > There is absolutely no trace of any commit-related log message in the log. Did > you try to commit as i asked? Otherwise the log is useless. > > Anyway, again, does it happen for all files? > If you run Subversion -> Show Changes action, what status displayed for the > file? > Can you also try to: > 1) make some modification in a file -> the file should turn blue and the diff > sidebar in editor should show the modification, right? > 2) run Subversion -> Revert Modifications -> everything should turn to uptodate > again, right? I didn't do the commit from inside NB, I did it from an external program. But it gets the diff information from the metadata files in the .svn folder, doesn't it? It seems like it does, because it correctly updates the sidebar highlighting.
> I didn't do the commit from inside NB, I did it from an external program. But > it gets the diff information from the metadata files in the .svn folder, > doesn't it? It seems like it does, because it correctly updates the sidebar > highlighting. No it doesn't. Subversion module does not listen on external changes. If you do any external operation (such as a commit) you should always resync in the IDE with Subversion -> Show Changes action. Thanks for understanding.
(In reply to comment #11) > > I didn't do the commit from inside NB, I did it from an external program. But > > it gets the diff information from the metadata files in the .svn folder, > > doesn't it? It seems like it does, because it correctly updates the sidebar > > highlighting. > No it doesn't. Subversion module does not listen on external changes. If you do > any external operation (such as a commit) you should always resync in the IDE > with Subversion -> Show Changes action. Thanks for understanding. If it doesn't, how does the sidebar highlighting get automatically updated? I can understand having to manually refresh the status, but as it is now, the coloring gets partly (and thus inconsistently) updated.
> If it doesn't, how does the sidebar highlighting get automatically updated? Does it? In the description of the issue you said it didn't: > After an SVN commit, the left sidebar coloring for the changed/removed/added lines in a file does not update.
(In reply to comment #13) > > If it doesn't, how does the sidebar highlighting get automatically updated? > Does it? In the description of the issue you said it didn't: > > After an SVN commit, the left sidebar coloring for the changed/removed/added lines in a file does not update. Sorry, not completely automatically, but reopening the file updates the sidebar coloring without using the Show Changes command. The filename coloring doesn't update until you run the command. So there's a slight inconsistency there... Wouldn't it be possible to add a "Scan for external changes" option as NB already does for files modified outside the editor?
(In reply to comment #14) > Sorry, not completely automatically, but reopening the file updates the sidebar > coloring without using the Show Changes command. The filename coloring doesn't > update until you run the command. So there's a slight inconsistency there... The diff sidebar is updated in this case simply because it is always freshly initialized when you open a file. It's not cached anywhere as file statuses are. > Wouldn't it be possible to add a "Scan for external changes" option as NB > already does for files modified outside the editor? Probably. With subversion 1.7 and its centralized metadata listening on external changes in metadata could be implemented. It would probably suffer from dramatic performance issues on large projects but you could turn it on manually on your own risk. If you really think it would be useful, reopen and change Issue Type to enhancement.
Enhancement request: Add a "Scan for external changes" option for source control highlighting as NB already does for files modified outside the editor.
*** This bug has been marked as a duplicate of bug 153559 ***