Bugzilla – Full Text Bug Listing
| Summary: | [Wziards] Previously entered comments not beeing remembered | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Stefan J. Morgenroth <dandracom> | ||||||
| Component: | CVS | Assignee: | platform-cvs-inbox <platform-cvs-inbox> | ||||||
| Status: | RESOLVED WONTFIX | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | Keywords: | helpwanted | ||||||
| Version: | 3.2.1 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | Macintosh | ||||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||||
| Whiteboard: | unreproducable | ||||||||
| Attachments: |
|
||||||||
|
Description
Stefan J. Morgenroth
*** Bug 105304 has been marked as a duplicate of this bug. *** Are you stil lseeing this. I've talked to a few other Mac users and they don't see this problem. If you still have the problem, could you look in the error log and see if there is anything there? Created attachment 26932 [details]
My error.log
Created attachment 26933 [details]
Screenshot of the situation
Well, I have nothing concerning in the error log but I attached the latest
messages I got I my error log.
Then I attached a screenshot.
not resolved for me. problem continues. Perhaps there is a permissions problem with the file in which the comments are persisted. The commit comment history is persisted in the file <your workspace>/.metadata/.plugins/org.eclipse.team.cvs.ui/commitCommentHistory.xml Does this file exist in your workspace meta-data area? If it does, what are the contents (i.e. do they look well formed like the sample below)? The file is written on shutdown. Another possibility is that the shutdown is failing for some reason. Shutdown Eclipse and try the following: - delete the commitCommentHistiry.xml file - recreate it with the following contents <?xml version="1.0" encoding="UTF-8"?> <CommitComments> <CommitComment>Comment 1</CommitComment> <CommitComment>Comment 2</CommitComment> </CommitComments> - restart Eclipse After you set the contents to the above, do the comments appear in the commit dialog? - commit a change and enter a new comment and then shutdown Eclipse Did the file get updated properly? Moving to REMIND to await your responses. Please reopen with your findings. Our usual practice is to move bugs to the RESOLVED REMIND state when there is not enough information provided to address the reported issue and more information has been requested. This bug has been in the RESOLVED REMIND state for quite some time so it is being CLOSED. If you can provide the requested information or you otherwise feel that this is still an issue, please reopen the bug. If you are unable to open it due to a lack or permissions, please add a comment to the bug stating that you would like to have the request reconsidered. I applogize for this blanket approach to bug screening but there are just to many bugs in the REMIND state for us to effectively triage them. Your help in this matter is appreciated. Sorry for missing this answer. This problem is stil alive. (In reply to comment #6) > After you set the contents to the above, do the comments appear in the commit > dialog? No. It continues empty. > - commit a change and enter a new comment and then shutdown Eclipse > > Did the file get updated properly? No update of the file so far. None of the files in the named Path were touched. :( Unfortunately, none of the Mac users I have talked to have been able to reproduce the problem. Until we can reproduce it, there is not much we can do. Could it be a problem by porting the configurations from a Windows (2000) to the Mac version? It could be. Did you copy a workspace from a windows machine to a Mac? Do you see the problem if you start with a fresh workspace? Well, I checked it out with a blank virgin workspace. Now it is a bit better. The comments are now written to the file with every change but the GUI is not willing showing the letters. The selection box after each commit has now a new blank line for each comment like those in the screenshot (https://bugs.eclipse.org/bugs/attachment.cgi?id=26933). By the way, I installed yesterday a clean new eclipse 3.2.1. Given that we have been unable to reproduce this problem, we do not intend on addressing it. |