Versioning of Server Project Content

    This section describes the most basic use cases of versioning server projects with two popular version control systems. It describes the way to use the particular version system and CloverDX Designer together. It does not serve to replace the documentation of any particular version control system.

    We encourage you to read the documentation for version control system tool of your choice as well.

    Versioning of Server Project Content

    Initial Check-Out of Project from Repository

    Adding Server Project to Version Control

    Connecting Server Project to Existing Repository

    Getting Changes from Repository

    Committing into Repository

    Server projects store files remotely and locally. This allows you to use version control system of your choice. You can use an Eclipse plugin as well as an external tool. The basic workflow of usage of Git and SVN versioning systems in CloverDX Designer is described below.

    Version Control System Files and Synchronization

    Version control system metadata files (e.g .svn directory) must not be synchronized between Designer and Server. These files avoided from synchronization are listed in Preferences under Ignored Files section. If you use Bazaar, Git, Mercurial, or SVN, you do not have to care about this, as it is already configured. If you use any other version control system, you should add its files and directories to this list of ignored files.

    Versioning Tools

    The following text describes the basic work flows with Git and SVN. For both, an approach with an Eclipse plugin (EGit, Subclipse), external GUI tool (TortoiseGit, TortoiseSVN) and command line utilities is described.

    EGit is an Eclipse plugin for versioning with Git. It is included in CloverDX Designer.

    Subclipse is an Eclipse plugin for versioning with SVN. Since it is not part of CloverDX Designer, you need to install it, e.g from Eclipse Marketplace.

    TortoiseGit and TortoiseSVN are external GUI tools.