anchor.diff:  
   Now you create a repository to store your project's files.
   
  -.  In the jMonkeyEngine SDK, right-click the project in the Projects window and choose Versioning &gt; Import Into Subversion Repository (or initialize Mercurial Project, etc, respectively).
  +.  In the jMonkeyEngine SDK, btn:[RMB] click the project in the "`Projects`" window and choose menu:Versioning[Import Into Subversion Repository] (or initialize Mercurial Project, etc, respectively).
   **  Tip: If you haven't evaluated yet which system to choose, start with Subversion for now.
   
   .  Go through the wizard and fill in the fields to set up the repository.
  
positive.code: 
  You and your team mates check out (download) the repository to their individual workstations.
  
  .  Go to the Team menu and choose Subversion &gt; Checkout (or Git or Mercurial respectively)
  .  Fill in your repo data into the wizard and click Finish.
  //**  A typical repository +++<abbr title="Uniform Resource Locator">URL</abbr>+++ looks like this example: `link:http://jmonkeyengine.googlecode.com/svn/trunk/engine[http://jmonkeyengine.googlecode.com/svn/trunk/engine]`
  **  If you want to be able to submit changes, you must have a username and password to this repository. Otherwise leave these fields blank.
  
  .  The repository is downloaded and stored in the location you chose.
  .  Use the File &gt; Open Project menu to open the checkout as project and start working.
  **  If the checkout is not recognized you need to choose File &gt; New Project from Existing Sources
  
  
  Of course you can also check out existing repositories and access code from other open-source projects (e.g. SourceForge, GoogleCode, dev.java.net).
  
negative.code: = jMonkeyEngine SDK: Version Control
  :revnumber:2.0
  :revdate: 2020/07/09
  :keywords: documentation, sdk, editor, tool
  
  
  Whether you work in a development team or alone: File versioning is a handy method to keep your code consistent, compare files line-by-line, and even roll back unwanted changes. This documentation shows you how to make the most of the SDK's integrated version control features for Subversion, Mercurial, and Git.
  
  For every team member, the file versioning workflow is as follows:
  
  .  Once: Download a working copy of the project from the repository ("`checkout`").
  .  Regularly: Upload your own changes to the repository ("`commit`").
  .  Regularly: Download updates by others from the repository ("`update`").
  
  include::partial$sdk-features-tip.adoc[]
  
  