Syncro SVN Client 4.2

Syncro SVN Client 4.2 is a software allowing authors or developers to easily share document and code content, which provides full SVN repository support including checkout, export, import, copy, mkdir, rename, branch, tag and delete.

You can browse repositories, check for changes, commit changes, update your working copy, examine the revision history in tabular form or as a revision graph, view the svn annotations, integrate it with bug tracking tools. Also you can examine the changes after a synchronize operation for text files or image files in a Compare View or see the differences between two revisions of a folder. SVN conflicts appeared after an update operation can be easily solved using the visual conflicts editing feature. There is no need to install separate applications like a Subversion command line client or a file compare tool.

Major Features:

1. Why Subversion?The advantages of the SVN version control system that recommend it as a replacement for the CVS system.
   • Subversion is a relatively new versioning system, designed as a replacement of CVS. Its features include:
   • • Atomic commits
     • The file Rename/Move/Copy actions preserve the revision history
     • The directories are versioned
     • Native support for binary files
     • Optimized repository access
     • File properties and MIME types
     • Multiple repository access protocols including HTTP and HTTPS.
   • Subversion is a good choice for sharing/storing large collections of XML files that change frequently. Subversion stores the differences between revisions in an efficient database and minimizes the network load footprint - only the differences are sent between the SVN client and the server.
2. Flexible Layout of the User Interface. The layout of the user interface can be arranged by dragging dockable and floating views in the window and outside the window of the application.
   
   • The Syncro SVN Client is composed of several views allowing you to browse the Subversion repositories and your local working copies, compare and merge modifications, check the revision history. All views are dockable, meaning that you can move them to create the optimal layout for your use case.
3. SVN Repository. Special view for managing SVN repositories accessed through different protocols: SVN, SVN+SSH, HTTP(S).
   • SVN Repository Browsing. You can add multiple SVN repositories to the list accessed through different protocols (SVN, SVN + SSH, HTTP(S)) and browse them in parallel. In this way you can identify the resources you need to checkout, or even create branches or tags directly in the repository.
   • Synchronize with SVN Repository. In the synchronize view you can see the overall status of your working copy resources when compared to the repository resources. The view focuses on incoming and outgoing changes, where incoming ones are the changes that other users have committed since you last updated your working copy. The outgoing changes are the modifications you made to your working copy as a result of editing, removing or adding resources.
4. SVN Resource History. The History view contains the revision number, author name, commit message and date of each revision of a file or folder from the SVN repository.
   • In Subversion, both files and directories are versioned and have a history. If you want to examine the history for a selected resource and find out what happened at a certain revision you can use the History view.
5. Local Working Copy of a SVN Repository.
   •  Each author that shares the SVN repository with other authors works on a local copy of the repository called a working copy of the repository. The local copy must be synchronized with the repository by committing the local changes to the repository and by updating the local copy with the changes committed by other authors on the repository.
6. Author Information at Line Level. For each line of a file stored on a SVN server the author (user name) and the revision number of the last change applied to that line is displayed.
   • Sometimes you need to know not only what lines have changed, but also who changed specific lines in a file. The Annotations view displays the author and the revision number that changed every line in a file the last time. The view is synchronized with the History view and the source code view: clicking in any view updates the current selection in the other two views so that the author name and the revision number are displayed for any line of the source code view.
7. Check Differences Between Local Version and Repository Version. Compare the local working copy version of a file with the SVN repository version.
   • One of the most common requirements in project development is to see what changes have been made to the files from your working copy or to the files from the repository. You can examine these changes after a synchronize operation with the repository, by using the Open in Compare Editor action from the contextual menu.
8. Resolving Conflicts quickly.
   • An update operation may bring the local copy of a file in a conflict state. The conflict state can be resolved more quickly if the conflicts are edited visually in a compare view which presents the two conflicting versions side by side like a Diff application. In the compare view the user decides for each conflict the variant which will remain and will be finally committed to the repository: the local one, the repository one or a manually edited combination of the two variants.
   • A merge operation also can create conflicts in a working copy. At the end of the merge operation all the conflicts can be resolved quickly in a dialog which lists all of them and allows selecting one of four possible resolutions for each conflict: Keep incoming, Keep outgoing, Mark resolved and Resolve later.
9. Revision Graph.
   • The history of a SVN resource can be viewed as a graph in the form of a tree. One node of the graph represents a revision of that resource committed to the trunk or one of the branches of the SVN repository. The icon and the background color of a graph node represent the operation that generated a revision. A graph node contains also the repository path and the revision number.
10. Directory Change Set. The Directory Change Set view presents a set with all the resources changed between two revision numbers of a SVN folder.
    • Sometimes a set with all the changes committed on any resource of a folder and its subfolders is needed. The user just selects a start revision number and an end one from the history of the folder and runs an action which computes the set of all these changes. The Directory Change Set view presents the set of changes in a tree format. The revisions corresponding to a resource from the tree are grouped in a separate list
11. Integration with Bug Tracking Tools. The commit message can include a bug ID which links the committed revision with a bug tracking tool. Special SVN properties configure the format and location of the bug ID in the commit message.
    • Users of bug tracking systems can associate the changes they make in the repository resources with a specific ID in their bug tracking system. When the user enters a commit message, a bug ID may be added to this message which links the committed revision with the bug entry maintained in the bug tracking system. The format and the location of the bug ID in the commit message are configured with SVN properties like: bugtraq:url, bugtraq:number, bugtraq:append, bugtraq:logregex.

Enhancements:

• Support for SVN 1.6. Syncro SVN Client supports SVN 1.6.2, allowing users to take advantage of the latest SVN improvements and fixes. Previous SVN versions are also supported, the user being able to decide whether a working copy should be updated to version 1.6 or not.
• Tree conflicts handling. Subversion 1.6 recognizes a new kind of conflict, known as a "tree conflict". Such conflicts manifest at the level of directory structure, rather than file content. These conflicts include deletions of locally modified files and incoming edits to locally deleted files. Syncro SVN Client allows to handle these conflicts offering a dialog that lists possible solutions for solving these conflicts.
• Improvements to svn:externals. Subversion 1.6 allows to link to external files by putting their URLs in the svn:externals property on the parent folder. Syncro SVN Client allows you to create, update, commit and remove external links from the user interface changing automatically the svn:externals property as needed.
• Improved revision graph performance. Syncro SVN Client stores the result of a revision graph operation and reuses that for further operations on the same repository, thus avoiding unnecessary requests to the SVN server for the same data. This results in a noticeable increase in performance.
• Access to network SVN file repositories. Network SVN repositories can be accessed using file URLs of the form "file://server/path".
• Better handling of symbolic links. Syncro SVN Client analyses the structure created by symbolic links usage detecting and handling infinite recursions.

Requirements:

• Minimum hardware configuration is Intel Pentium III system with 128 MB of RAM and 200 MB free disk space.
• Syncro SVN Client may work very well with JVM implementations from other vendors but the eventual incompatibilities will not be solved in further Syncro SVN Client releases.