SvnTask – A New Ant Task for Subversion

I like it when people email me cool stuff.  Today Jon emailed me about adding his new project SvnTask to my Ant wiki.

SvnTask is a super simple solution for using svn from ant. I just want a 100% Java solution that uses the nice svnkit library. Include two simple jar files and go.

I haven’t tried it yet but will give it a shot tomorrow!  It’s open-source and hosted on Google Code so you can checkout the code and contribute your own patches.

Recent Related Posts

15 thoughts on “SvnTask – A New Ant Task for Subversion

  1. Hey Jim, can you post more examples of an ANT sync between two windows machines? I can sync just fine in ANT on the same box but not sure how to sync between two different machines using an ANT build file.

  2. @Noah – how are you connected between the two machines? FTP? Mapped drive? There are several tasks in Ant that should be able to handle any kind of file transfer…

  3. We have a collection of Windows servers on our internal network. We export our SVN repository on the local server just fine and then would like to copy that export to another machine. We have mapped drives but they don’t seem to work in ANT. Any suggestions?

  4. I don’t know what I was doing wrong, but it was as simple as just mapping a drive and then calling it in my fileset.

    This is a test

    Thanks for asking if I was using a mapped drive. It was that easy.

  5. The only problem I have with this is that it requires a user logged into the server for the mapped drives to work. I have my ANT tasks running automatically 4 times a day and the server is sometimes locked. When this happens then the mapped drives don’t work, am I missing something?

  6. We are running our Ant tasks on a Windows 2003 server on our internal network. It works great when we are logged in but we don’t want to have the server logged in all the time. We would prefer it locked most of the time unless one of our IT staff is using it.

  7. I figured it out by just calling it by machine name.

    using the destination directory as \\testserver\directory path seemed to work. Just don’t forget to make sure the directory has the correct permissions to allow for the sync.

    Hope this helps.

  8. it appears so, it seems that calling a mapped path like for example: G:\test\builddir will only work when you are logged in for that mapped drive to take effect. The UNC seems to work all the time.

    I hope this cuts down the headaches for other people that might read this.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>