Community
Participate
Working Groups
Build ID: eclipse 3.4.1 Steps To Reproduce: 1.Open file backed by CVS 2.Coloured bar in left side showing CVS information on each line can be opened with Right click -> Team -> Show annotation 3.No preference can be found to enable this functionality on ALL files opened from CVS More information: For software legacy maintainers it is very beneficial to see version control information available to a given source file, and currently this must be manually enabled for each file opened in each new Eclipse session. It would be very nice to have this functionality optionally enabled by default on all files backed by CVS.
The main reason for not being enabled by default is performance. However, we could do it in the background.
> Right click -> Team -> Show annotation If you use this often, you might want to assign a keybinding to the command. I use Alt+Shift+A.
(In reply to comment #1) > The main reason for not being enabled by default is performance. However, we > could do it in the background. I agree that the default configuration should concentrate on performance for the many. I would personally not mind taking the performance hit, if I'd explicitly enabled this myself in a preference panel. Our CVS-server is in the next room. Another possible place could be on each CVS repository as some are nearby and others very distant.
Note that it's not only a concern of your workspace but also a question how hard the CVS server will be hit if many people enable the feature.
(In reply to comment #4) > Note that it's not only a concern of your workspace but also a question how > hard the CVS server will be hit if many people enable the feature. I am aware of that. Hence the default setting of off. In our group it would be perfectly fine to have this on for all developers.
I guess Team team could already do this. They would simply have to listen for editors being opened, then fetch annotate information and display in on the editor using ITextEditorExtension4. (In reply to comment #1) > The main reason for not being enabled by default is performance. However, we > could do it in the background. The annotate information is already fetched in the background, so there wouldn't be any additional concurrency issues. (In reply to comment #3) > Another possible place could be on each CVS repository as some are nearby and > others very distant. Enablement per project or per repository would be required - otherwise, you could really put some load on those sourceforge servers...
>The annotate information is already fetched in the background, so there >wouldn't be any additional concurrency issues. Right. I was also thinking of the server. Though not processing the requests in the bg it might want to give it lower prio.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
