Kohsuke Kawaguchi's Blog

Introducing wagon-svn

I just published the wagon-svn project, a Maven wagon implementation that talks to a Subversion repository directly. This enables Maven2 users to deploy artifacts and push website contents to a Subversion repository in a fully automated fashion.

The main motivation for writing code is for our projects on java.net. First, the web contents of java.net projects are controlled under Subversion/CVS, so we had no easy way to do mvn site:deploy. Wagon-svn fixes this. Second, our java.net projects couldn't directly deploy to the java.net maven2 repository (see the linked page for the workaround we had to do), which wagon-svn also fixes.

I've been using this in several of my projects already (such as Hudson) successfully, thanks to a few folks who served as guinea pigs — Paul Sterk and Stephen Connolly most notably.

The docs on the site explains how you need to update your POM to use this for your java.net projects. Finally, if you find this useful, you might find my java.net skin project useful too.

Comments

• We are already using on the jain-sip project. Thanks for putting this up. This is good news for the java.net maven2 users and really great work.

  Posted by: deruelle_jean on November 08, 2007 at 12:35 PM

• We at Sourcesense (http://www.sourcesense.com) are already using our svn as m2 repo, with the additional advantage of keeping only one authorization/permission server side list for svn and maven, i.e. dav_svn_authz).
  This can be achieved with the wagon-webdav provider (http://maven.apache.org/wagon/wagon-providers/wagon-webdav/ ) which I had to minimally fix for some too verbose (stacktraces logged for warns) logging, but that provides already capabilities of writing on svn (being in the end webdav).
  We also tried wagon-scm provider (http://maven.apache.org/wagon/wagon-providers/wagon-scm/l) in the past which *should do* exactly what you are trying to achieve here, but it's completely broken.
  Would it make sense to contribute this back to maven for integration with existing (and maybe already widely used) plugins?

  BTW, cool job man! Maven rocks...

  Posted by: mindthegab on November 09, 2007 at 01:57 AM

• 
  I saw some reports indicating that wagon-webdav won't work with Subversion, but sounds like you are saying that it works. In that case I really should have tried that.

  
  I indeed tried wagon-scm, and besides the fact that it has problems, as you noted, the fundamental issue with wagon-scm is that it checks out the whole things even when you are uploading. On projects like Hudson, where we already have some 150 releases in the subversion repository, checking out everything just to upload one more (and multiply that by the number of artifacts, then further multiply that by 3 for checksums) is way too slow.

  Posted by: kohsuke on November 09, 2007 at 10:52 AM

This work is licensed under a Creative Commons License.