<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SVN on David Hamp-Gonsalves</title><link>https://davidhampgonsalves.com/tags/svn/</link><description>Recent content in SVN on David Hamp-Gonsalves</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 25 Aug 2011 00:00:00 +0000</lastBuildDate><atom:link href="https://davidhampgonsalves.com/tags/svn/index.xml" rel="self" type="application/rss+xml"/><item><title>Connecting to SVN with Scala/Java</title><link>https://davidhampgonsalves.com/connecting-to-svn-with-scala/java/</link><pubDate>Thu, 25 Aug 2011 00:00:00 +0000</pubDate><guid>https://davidhampgonsalves.com/connecting-to-svn-with-scala/java/</guid><description>&lt;p&gt;I needed to do some SVN scraping recently to automate the detection of certain areas of code and this is what I learned.&lt;/p&gt;
&lt;h2 id="libraries"&gt;Libraries&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;SVNKit&lt;/strong&gt; was too low level for my(and I suggest most) needs. I found I was writing quite a bit of code for relatively simple actions.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;SvnClientAdapter&lt;/strong&gt; provides a simplified interface for either the cmd line client, SVNJavahl or SVNKit. Its my recommendation that for most projects this is the best way to go. In my case I used SVNJavaHL as my low level SVN library.&lt;/p&gt;</description></item></channel></rss>