Syncro SVN Client v5.1 for Windows, Linux & MacOSX – Features

syncro-svn-client-v51

Syncro SVN Client makes easier the document and code sharing between content authors or developers. This multiplatform Subversion front-end allows you to browse repositories, check for changes, commit changes, update your working copy and examiner the revision history. The Syncro SVN Client was initially developed as an embedded application in the XML Editor and starting with version 8.1 of the editor it is available also as a separate product.

Features
• Why Subversion?
– The advantages of the SVN version control system that recommend it as a replacement for the CVS system.
• 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.
• SVN Repository
– Special view for managing SVN repositories accessed through different protocols: SVN, SVN+SSH, HTTP(S).
• 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.
• Local Working Copy of a SVN Repository
– Each author that shares the SVN repository with other authors works on local versions of the repository resources called a working copy of the repository. The changes applied to the local copy of the repository must be synchronized with the repository hosted on the SVN server.
• 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.
• Check Differences Between Local Version and Repository Version
– Compare the local working copy version of a file with the SVN repository version.
• Visual Conflict Editing
– Visually edit the conflicts generated in the local version of a file by an update operation.
• Revision Graph
– The history of a SVN resource can be viewed as a graph in which a node represents one revision of the resource committed to the trunk or a branch of the SVN repository.
• Directory Change Set
– The Directory Change Set view presents a set with all the resources changed between two revision numbers of a SVN folder.
• 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.

Home Page – http://www.syncrosvnclient.com/

Tagged : / / / / / / / / / / / / / / /

Syncro Soft Announces New Release of Syncro SVN Client

syncro-svn-client

Syncro Soft Announces New Release of Syncro SVN Client

Syncro Soft Ltd, the producer of Syncro SVN Client, has announced the immediate availability of version 5.1 of its Subversion (SVN) client.

PR Log (Press Release)Mar 15, 2010 – Release date: March 15, 2010

Version 5.1 of Syncro SVN Client improves working copy load time, automatically refreshes the working copy on external file changes, makes repository browsing more responsive, adds support for repository imports at file level, adds support for replacing resources, improves handling of obstructed resources, improves history support, allows creating branches/tags directly from the repository and offers options to print or save as image a revision graph.

For the complete list of features please visit http://www.syncrosvnclient.com

New in version 5.1:

A working copy is cached, so when it is loaded next time in the Working Copy view, the operation will be much faster than in the previous versions of Syncro SVN Client.

The working copy is automatically refreshed if changes are detected in the file system. This is done in order to update the state of the resources modified by external applications.

You can configure the repository connections timeout and stop non-responsive repository browsing operations.

Added support for importing files into a repository.

Working copy resources can be replaced with their HEAD or BASE revision.

Operations correctly take into account obstructed resources.

The history for a resource deleted from the repository but which is still present in the working copy is now displayed by properly detecting the revision at which the resource was deleted.

The Branch/Tag action can be performed directly on the repository, without having a working copy previously checked out.

Generated revision graphs can be printed or saved as images.

Pricing and Availability
Syncro SVN Client with One Year Maintenance Pack costs $59
Syncro SVN Client Site License with One Year Maintenance Pack costs $2970
Volume discount rates are available starting with 5 licenses.

Syncro SVN Client can be run on Windows, Mac OS X, Linux, Solaris.

To purchase please visit the Syncro SVN Client store at
http://www.syncrosvnclient.com/buy.html
Syncro SVN Client 5 can be freely evaluated for 30 days from
http://www.syncrosvnclient.com/download.html

About Syncro Soft LTD

Syncro Soft is a privately held software company founded in 1998 with a large area of expertise in XML technologies: XML Schema, Relax NG, Schematron, XSLT, XPath and XQuery. The main product oXygen XML Editor provides the best coverage of the today XML technologies; it complies with the established standards released by W3C and other organizations and enhances developer productivity through an intuitive and innovative XML IDE. Syncro Soft is a member of W3C.

oXygen is a registered trademark of Syncro Soft in the U.S and other countries. Subversion is a trademark of CollabNet. Any other trademarks or service marks contained herein are the property of their respective owners.

SOURCE: Syncro Soft Ltd.
support@syncrosvnclient.com
http://www.syncrosvnclient.com/

# # #

Syncro Soft provides consulting services that are focused on creating Java based XML solutions. Other aspect is the integration of the XML Editor within your content management system.

Tagged : / / / / / / / / / / / / / /

ANT Builds and Subversion (SVN) | Ant integration with Subversion guide

ant-builds-and-subversion

As I have mentioned in a previous blog entry, I have come to love using ANT in my development environment. One of the things that I like about it is how well it integrates with my Subversion repository using SVNAnt. If you are not using either ANT or Subversion, you owe it to yourself and your team to check it out.

Here we’ll go over a simple build script that exports application files from the Subversion repository into a local folder in the CFEclipse project. You can then view the following entry on how to ftp that into your production/staging server.
First we need to make sure that your ANT install has the necessary SVNAnt jar files. You can download them here: http://subclipse.tigris.org/svnant.html. Once you unpack the svnant-1.0.0.zip file, you’ll find three jar files: svnant.jar, svnClientAdapter.jar, svnjavahl.jar. Place them on your
[ANTInstall]/lib* folder.

Once you have the jar files in place, you can define them in your build file’s property section like so:
<!– svnant lib –>
<property name=”svnant.lib” value=”lib” />
<property name=”svnant.jar” value=”${svnant.lib}/svnant.jar” />
<property name=”svnClientAdapter.jar” value=”${svnant.lib}/svnClientAdapter.jar” />
<property name=”svnjavahl.jar” value=”${svnant.lib}/svnjavahl.jar” />
Followed by this path definition after all your properties have been defined:

<!– path to the svnant libraries. Usually they will be located in ANT_HOME/lib –>
<path id=”project.classpath”>
<pathelement location=”${svnjavahl.jar}” />
<pathelement location=”${svnant.jar}” />
<pathelement location=”${svnClientAdapter.jar}” />
</path>

Now all you have left to do is add the following task definition:
<!– load the svn task –>
<taskdef resource=”svntask.properties” classpathref=”project.classpath”/>

Now you are all set! You can now call tasks like the following export target:

<!– define properties –>
<!– svn repo url –>
<property name=”svn.url” value=”http://[mysvnhost]/svn/repo/myprojectFiles/” />
<property name=”svn.exportPath” value=”[yourDirectory]:\\[pathToYourCFEclipseProject\\build” />

<target name=”svn.export”>
<echo message=”Exporting application files from svn repository:” />
<input message=”Please enter svn repo username:” addproperty=”svn.username” />
<input message=”Please enter svn repo password:” addproperty=”svn.password” />
<mkdir dir=”${svn.destPath}” />
<svn username=”${svn.username}” password=”${svn.password}”>
<export srcUrl=”${svn.url}” destPath=”${svn.exportPath}” revision=”HEAD” />
</svn>
<echo message=” … finished exporting files.” />
</target>

That’s it. No more running command line tasks to get your subversion commands. For additional info and other SVN tasks you can go to http://subclipse.tigris.org/svnant/svn.html

Tagged : / / / / / / / / / / / / / / / / / / /

How to Use SVN Tasks with ANT ?

svn-tasks-with-ant

This post is about using ANT to perform some of the most common source-control related tasks such as export, tagging, and branching. I am using ANT version 1.7.0 and SVN Ant version 1.1-rc3, bound against Subversion 1.4.0.

The related software can be downloaded here:
1.    SVN Ant = http://subclipse.tigris.org/svnant.html
2.    ANT = http://ant.apache.org/
I shall start with build.properties, which lists a few key/value pairs used in our SVN Ant task build file, referred as svn-tasks.xml:

Content of build.properties:
####START of SVN Properties ####
svn.repository.url=http://xyz.com/repos/somereponame
svn.project.base.path=someprojectname
svn.username=user name to access repo
svn.password=password to access repo
#This shall be name of the tag,
#This property should always be updated before build starts
#This property shall be used to export
tag.name=SOME_TAG_NAME_12222008
#This shall be name of new branch,
#this property should be used only when new branch is to be created
new.branch.name=NEW_BRANCH_12222008
####END of SVN Properties ####
Content of svn-tasks.xml:
<property file=”build.properties”></property>

<!– SVN and SVN-ANT Tasks properties –>
<property name=”svn.repository.url” value=”${svn.repository.url}”/>
<property name=”svn.project.base.path” value=”${svn.project.base.path}” />
<property name=”svn.base.url” value=”${svn.repository.url}/${svn.project.base.path}”/>
<property name=”svnant.lib.dir” location=”svn-ant-lib”/>
<property name=”svnant.javahl” value=”false” />
<property name=”svnant.svnkit” value=”true” />
<!– SVN and SVN-ANT Tasks properties –>

<!– *************************************************************** –>
<!–   Set-Up of SVN-ANT classpath                                   –>
<!– *************************************************************** –>
<path id=”svnant.classpath”>
<fileset dir=”${svnant.lib.dir}”>
<include name=”**/*.jar” />
</fileset>
</path>

<!– *************************************************************** –>
<!–   Loading of SVN task                                           –>
<!– *************************************************************** –>
<typedef resource=”org/tigris/subversion/svnant/svnantlib.xml” classpathref=”svnant.classpath” />

<!– *************************************************************** –>
<!– tool-availability: Determine if SVN-ANT is available.           –>
<!– *************************************************************** –>
<target name=”tool-availability”>
<available resource=”org/tigris/subversion/svnant/svnantlib.xml”
classpathref=”svnant.classpath”
property=”available.svnant”
/>
<echo message=”SVN-ANT is available = ${available.svnant}”/>
</target>

<!– **************************************************************** –>
<!– does-svnant-exist: depends on tool-availablility and     –>
<!–                    displays error message                                   –>
<!– ***************************************************************** –>
<target name=”does-svnant-exist” depends=”tool-availability”>
<fail unless=”available.svnant”>
SVN-ANT is not available, cannot perform tagging or checkout/export svn ant task.
</fail>
</target>

<!– ****************************************************************** –>
<!– svntag: performs tagging using properties from                              –>
<!–         build.properties and uses SVNANT tasks                              –>
<!– ******************************************************************* –>
<target name=”svntag” description=”tags individual project using svnant task”>
<property name=”svn.tag.message” value=”Tagging Project ${project.name} with tag name ${tag.name} from trunk “/>
<property name=”src.url”  value=”${svn.base.url}/${project.name}/trunk/”/>
<property name=”dest.url” value=”${svn.base.url}/${project.name}/tags/${tag.name}”/>

<echo message=”${svn.tag.message}”/>
<echo message=”${src.url}”/>
<echo message=”${dest.url}”/>

<svn javahl=”${svnant.javahl}” svnkit=”${svnant.svnkit}” username=”${svn.username}” password=”${svn.password}”>
<copy srcUrl=”${src.url}” destUrl=”${dest.url}” message=”${svn.tag.message}”/>
</svn>
</target>

<!– ****************************************************************** –>
<!– svnexport: performs export using properties from                            –>
<!–            build.properties and uses SVNANT tasks                           –>
<!– ****************************************************************** –>
<target name=”svnexport” description=”exports individual project using svnant task”>
<property name=”svn.tag.message” value=”Exporting Project ${project.name} with tag name ${tag.name}”/>
<property name=”src.url”  value=”${svn.base.url}/${project.name}/tags/${tag.name}”/>
<property name=”destPath” value=”${dest.path}”/>
<echo message=”${svn.tag.message}”/>
<svn javahl=”${svnant.javahl}” svnkit=”${svnant.svnkit}” username=”${svn.username}” password=”${svn.password}”>
<export srcUrl=”${src.url}” destPath=”${destPath}/${project.name}”/>
</svn>
</target>

<!– ****************************************************************** –>
<!– svnbranch: creates a new branch using properties from                       –>
<!–            build.properties and uses SVNANT tasks                           –>
<!– ****************************************************************** –>
<target name=”svnbranch” description=”creates a new branch for individual project using svnant task”>

<property name=”svn.branch.message” value=”Creating new branch for
Project ${project.name} with new branch name ${new.branch.name} from
trunk”/>
<property name=”src.url”  value=”${svn.base.url}/${project.name}/trunk/”/>
<property name=”dest.url” value=”${svn.base.url}/${project.name}/branches/${new.branch.name}”/>

<echo message=”${svn.branch.message}”/>
<echo message=”${src.url}”/>
<echo message=”${dest.url}”/>

<svn javahl=”${svnant.javahl}” svnkit=”${svnant.svnkit}”
username=”${svn.username}” password=”${svn.password}”>
<copy srcUrl=”${src.url}” destUrl=”${dest.url}” message=”${svn.branch.message}”/>
</svn>
</target>

Link: http://java.dzone.com/articles/how-use-svn-tasks-with-ant

Tagged : / / / / / / / / / / / / / / / / /

SVN Installation | Subversion Installation guide | Subversion Setup

Install CollabNet SVN Command Line Client in Red Hat

Link: http://www.collab.net/downloads/subversion/redhat.html

1. Platform and configuration

Product: CollabNet Subversion client

Platforms: Red Hat Enterprise Linux releases 4 and 5 (all versions, 32 bit)

Prerequisite: You must be a superuser (root) to install and uninstall

CollabNet Subversion.

2. Import CollabNet GPG key

CollabNet Subversion RPMs are signed using our GPG key. As a one-time task,

import the CollabNet GPG key using the command:

    sudo rpm –import /path/to/RPM-GPG-KEY-csvn.asc

The CollabNet GPG key is available for download at:

http://www.collab.net/nonav/downloads/subversion/gpg-key/RPM-GPG-KEY-csvn.asc

3. First installation

The command to install the CollabNet Subversion RPM, if a previous version

has not already been installed, is:

    sudo rpm -ivh /path/to/client.rpm

4. Updating an existing installation

If you have a previous version of the CollabNet Subversion client RPM installed,

update to the new version by running this command:

    sudo rpm -Uvh /path/to/client.rpm

If you also have a previous version of the CollabNet Subversion server RPM

installed, add the –force option to the command:

    sudo rpm -Uvh –force /path/to/client.rpm

5. Post-installation instructions

A. CollabNet Subversion installs into /opt/CollabNet_Subversion, which is

   probably not on the executable search path for your system. Add the directory

   /opt/CollabNet_Subversion/bin to your $PATH environment variable. In order to

   make this change affect all users of your system and persists across reboots,

   add the following line to /etc/profile:

    PATH=/opt/CollabNet_Subversion/bin:$PATH

B. CollabNet Subversion provides man pages and localizations for several

   languages. To take advantage of these features, update your MANPATH and/or

   LOCPATH environment variables to include the CollabNet Subversion directories.

   For example:

    export MANPATH=/opt/CollabNet_Subversion/share/man:$MANPATH

    export LOCPATH=/opt/CollabNet_Subversion/share/locale:$LOCPATH

6. Support for CollabNet Subversion

Find out about CollabNet Technical Support at

http://www.collab.net/services/subversion/

Information about CollabNet Training, Consulting, and Migration

services is at http://www.collab.net/services/subversion/training.html

Join openCollabNet for community support: http://open.collab.net

Setup SVN proxy setup

After Successful installation of SVN

Step 1: Go to /root  ex. $ cd /root

Step 2: List the all the hidden files.

Ex. $ ls –a

You will be getting .subversion folder underneath.

Step 3: go to ./subversion

Ex: $ cd .subversion

Step 4: List all the files under .subversion folder

$ ls

Step 5: Open severs file with vi editor

$ vi services

Step 6: Scroll down to [global] section and make the changes by uncommenting follwing lines and putting proxy information.

http-proxy-exceptions =

http-proxy-host =

http-proxy-port =

http-proxy-username =

http-proxy-password =

Step 7: Save and exit the vi editor

Tagged : / / / / / / / / / / / / / / / / / /