[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Java Question

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-08-02 03:04:35 CEST

Daniel Rall <dlr@collab.net> wrote on 08/01/2006 06:50:43 PM:

> On Tue, 01 Aug 2006, Dan Pozmanter wrote:
>
> > Hmmm, that sounds nice. I suppose I am biased towards dev time
itself.
> > I will be able to go straight in without auth.
>
> Okay. Subversion has two layers which you might be interested in --
> libsvn_repos, and libsvn_fs. It sounds like libsvn_fs would be more
> useful to you. Should also/instead expose a repos layer, or is
> SVNClient sufficient API here?

I would like to be able to do some of this stuff from a "client", so that
would mean I would need libsvn_repos .. right?

For example, I would like to be able to create multiple directories in the
repository with one commit. Would also be nice to copy/move multiple
items in the repository with one commit. For example, when I need to make
a tag of the Subclipse project I need to do this:

svn mkdir url://tags/subclipse/X.Y.Z
svn copy url://trunk/subclipse url://tags/subclipse/X.Y.Z/subclipse
svn copy url://trunk/svnclientadapter
url://tags/subclipse/X.Y.Z/svnclientadapter

I usually just do it in the WC and then commit, but it would be nice to be
able to build a UI that could do it against the repository.

I think it would be cool to have some of this added, but I also think the
current approach to JavaHL makes the most sense. I really wonder how well
a Java class with all of these JNI calls would perform. For a lot of
operations, it would not matter but I sure wouldn't want to do working
copy status checks this way.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 2 03:05:22 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.