Check-in my project to source control

4 posts / 0 new
Last post
Vasily Zakharov
Jolaf's picture
Offline
Mobile Conjurer
Joined: 6 Apr 2010
Posts:
Check-in my project to source control

I've created a workspace and a project with few files, and now I want to put my project under source control system.

However, MoSync created a bunch of its own files, and I wonder which ones of them I should put to source control (so that I could continue development from the same point in the same context on some other machine), and which ones are in fact temporary and can be easily reconstructed.

Particularly, I see:
.metadata directory in the workspace root
.settings directory in the project root
.cproject, .mosyncproject, .project, .mosyncproject.local files in project root.

Which of them I should check in, and which I should not?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Sam Pickard
rival's picture
Online
Mobile Archmage
Joined: 19 Mar 2009
Posts:

You can check in all of these, but don't check in Output or FinalOutput folders.

Vasily Zakharov
Jolaf's picture
Offline
Mobile Conjurer
Joined: 6 Apr 2010
Posts:

Ok, thanks!

Fredrik Eldh
Fredrik's picture
Offline
Mobile Sorcerer
Joined: 16 Feb 2009
Posts:

Actually, you should only check in .cproject, .mosyncproject and .project.

.mosyncproject.local was made especially for local settings that should not be shared with other programmers. Also, the .workspace and .settings directories contain computer-specific information and should not be checked in.