Is there a bug in CCS 5.1 for debug configuration with version control systems? When I try to modify the debug configuration through Project->Properties->General, and specifically try to change the Connection (emulator), it doesn’t save the settings, but acts as if it does. After some digging around, I noticed that the .ccsproject file was write protected. I also noticed that it should automatically be changing the F28M35M52C1.ccxml file to match the chosen emulator, but that doesn’t change, since it was write protected as well.
The files were write protected because I have them in version control. By default, files cannot be changed, unless they are marked for edit by our version control software. The base Eclipse IDE knows when its own project files are being modified (.project, .cproject, and various .settings) and it automatically checks them out. However, the CCS plugins to Eclipse do not do that. I have also checked this with a project not under revision control. If a file is write protected, the CCS plugins act as if the file is being modified, but nothing actually happens.
Before CCS attempts to modify a file, it should be checking to see if it is writable, and at the very least, notifying the user that it can’t update settings due to write protection. It would be even better if it could use Eclipse to see if it is editable, and if not, use Eclipse’s built in “Team” tools to check it out from the server.
If I could get any information on how to fix this issue, I would appreciate it.
