Community
Participate
Working Groups
After doing a feature update in Eclipse last monday, i recognized, that the CVS keywords are not updated anymore, e.g. $Id:$ stays $Id:$, $Id: ... (valueold) ...$ stays $Id: ...(valueold) ...$, same with other CVS keywords like $Revision$, $Date$, $Author$, etc. I tried to "Restore Defaults" in Preferences > Team > CVS and also played with several "Default keyword substitution:" values, but the CVS keywords are not replaced/updated anymore ... :-( Eclipse 2.0.2, Build id: 200211071448
Whar CVS server version are you using?
Server: cvsnt_1.11.1.3.exe This worked for former Eclipse version...
What previous Eclipse version do you mean? 2.0 or 2.0.1? If so, there was no changes in thgis area between these releases. Just out of curriosity, what is the keyword expansion mode on the files in question (to see the mode, select Properties from the popup menu of a file and click on the CVS tab).
2.0.1. I checked the keyword expansion mode of a file (didn't know that this info is there for a file properties): it is "ASCII without keyword substitution (-ko)" ... now, where does this come from? I set in Preferences > Team > CVS > Default keyword substitution to "ASCII with keyword expansion (-kkv)". so, how can i tell the files to use the preferences setting? and why is it possible that files get another keyword substitution that set in preferences for Team > CVS? how can i "fix" my files to use the preferences setting?
Any new files will use the preference setting. Other files use the setting from the server. To change the setting on the server, use the Team>Change ASCII/Binary Property menu item.
Team>Change ASCII/Binary Property menu item is set to "automatic" which says "Automatically chooses 'Binary (-kb)' or 'ASCII with keyword expansion (- kkv)' for each file according to the Team file extension preferences." So how is it possible that such a file has "ASCII without keyword expansion (-ko)"? i didn't change such settings, as we always have the same (automatic/ASCII with keyword expansion) for all files in our projects. so, this could be an eclipse issue, couldn't it?
From your previous post, it seems you have misinterpreted what the Team>Change ASCII/Binary Property does. The default substitution mode is set on the Window>Preferences/Team>CVS preference page and is applied only to new files. Out of the box, the default in 2.0.2 is -ko. This has been changed in 2.1 to be -kkv. The Team>Change ASCII/Binary Property wizard is a tool which will allow you to change the keyword substitution mode of existing files which is what you probably want to do to correct the situation. Settings on the wizard have nothing to do with what Eclispe does to new files and nowhere else in Eclipse is the substitution mode changed on existing files. Although it is always possible that there is an issue with Eclipse, my guess is that somehow the keyword substitution mode on the server got changed (which can only be done using the above mentioned wizard or the "cvs admin" command) or someone created a new file and the mode was set to -ko because that was the default. The reason I doubt that it is an Eclipse issue is because there have been no other problems of this sort reported and this is a widely used feature. Also, there is nothing in this bug report that would be helpful if it turned out to be an Eclipse issue. To state this another way, if you can provide compelling evidence that this is an Eclipse issue, please reopen.
