• Locked Locked
  • Replies 5 replies
  • Subscribers 55 subscribers
  • Views 756 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCSv5.2 doesn't update workspace from .project checked out from subversion

Joachim Wiesemann
Prodigy 180 points

Hi,

we work on projects as a team. Thus we use subversion to keep all coworkers synchronized.

We added the .project files of the CCS projects to the repository. If someone add new files / deletes obsolete ones the changed .poject file is commited. All others check out the new .project file (while CCS is closed). But when opening the workspace again the changes in the project don't show up!

The only way we have found to update the workspace due to changes in the project is to delete the project and import it again. This has to be done manually which leads to problems, when forgotten!

Best Regards,

Joachim

  • TI__Guru**** 162975 points

    Joachim,

    Are you using the subeclipse (or another) subversion client plug-in for Eclipse so that CCS is away of which files are under revision control?

    In this capture I have 2 separate running instances of CCS (different workspaces).  In the one in the foreground I have added a new file to my project (new_test_file).  You can see that it has a "?" beside it as it is not yet managed.  The CCS in the background is not aware if it yet (rightly so since I have not committed the change).

    This screen capture is just the second instance of CCS.  I have now added the file to the respository.  I did this by right clicking on it and selecting the appropriate action from the Team menu.  Note that it now has a + beside it.  The other CCS is still not aware of it.

    This screen capture is still the second instance of CCS.  Now I have committed the change.  The little + has been replaced the the yellowish repository marker.

    Now if I go to my other CCS and do an update to HEAD I can see the new file.  Here is a screenshot of the 2 CCS instances:

    As you can see the other CCS can see the file now.

    Note that I could reduce the number of steps by instead of doing an add and then a commit I could just do a commit and it would add and commit it in 1 step.

    Regards,

    John

  • in reply to JohnS
    Prodigy 180 points

    John,

    I'm not using the subeclipse (or another) subversion client plug-in for Eclipse because I mostly use the eclipse headless build.

    (I'm using a different IDE and only start eclipse for changes in project settings. I hoped epclise was acting reliably on files but it seems to do it's own magic.)

    Currently I think changing to make and command line compile could be a great enhancement.

    Best Regards,

    Joachim

  • in reply to Joachim Wiesemann
    Guru 56178 points

    Stumbled on this week ago and thought it may relate to this issue - it seemed odd keeping any work space history but what do I know.

    I lowered it to 0 days while troubleshooting why something would not go away in the PE.

  • in reply to Genatco
    TI__Guru**** 162975 points

    Brett,

    The local history is a feature that keeps track of changes that you make to your source.  Kinda like a mini-revision control system.  Basically when you save it keeps track of the changes and you can compare your current file to one in the history or revert to one from the history.

    Personally I find it a good complement to revision control.  With revision control you can look at previous versions you have checked in / committed but the reality is that you make many changes before you check in.  The local history bridges that gap so that if you mess up inbetween check-ins and need to rollback you can do it.

    Regards,

    John

  • in reply to JohnS
    Guru 56178 points

    Hi John, Very interesting info will keep that in mind and look for aged events roll back buttons drop down list - hope it works both ways because I'm a lot like some politicians we have recently come to know constantly flip flopping back and forth until I've convinced myself the changes actually worked.