If you have connected to a repository, you are now able to share your solutions (which are Eclipse projects) with other developers by putting them in the repository.
You can also connect to the repository as part of the sharing process, but it is normally good practice to make sure that you can connect and that your repository is available before sharing it. |
Best practices dictate that you should enter a short comment for every revision to provide information on what was worked on. Many SVN tools use the revision comments to provide project visibility, such as email digests with revision summaries. Some tools even will integrate special notation in the comments to project management actions (i.e. ticket resolution). |
The resource project is a separate project in Servoy Developer and must be uploaded to the repository separately. This project contains style, database, and i18n information and should be shared over all the developers. |
Best practice would be to put any projects in the workspace into the trunk. This would be the main application project, any modules, and the resource project. If you are building multiple applications, you should consider using multiple workspaces, especially if the resources (database, styles, etc.) are different. |