news <email@example.com> wrote on 04/18/2005 11:37:40 AM:
> > You should always specify a root URL, but it will not have any impact
> > checkout to my knowledge. Why do you have to specify it? There isn't
> > a Subversion API to determine it programmatically, and there are
> > where it is handy to just run a command against the root URL.
> OK. I use TSVN and there is no need to supply root URL. But TSVN is not
> bound to any IDE, maybe Eclipse plugin needs it.
It isn't critical, but it works better when you have it. For example, say
you want to see the diff or log of a specific rev in the repository. You
can specify the complete URL to a specific path, but if it turns out that
path was not part of that revision, or does not exist at HEAD, you will
get an error. A CLI user would just type the root URL because that is all
you need if you are specifying a specific revision. We try to do the
same. It just helps avoid problems that the GUI can get you into. There
are a few cases where TSVN suffers the same problem. I think that they
now have a low-level API they can use to get the repository root (I know I
have seen them ask for it.) The JavaHL API only makes available a very
small and specific subset of the Subversion API. If we want to use a new
feature we have to ask for it, wait for it to be added to JavaHL (or add
it ourselves) but then also wait for it to make its way to a release of
Subversion. In some cases, it is easier to solve the problem other ways.
> > How you structure your repository is up to you. There is no real
> > significance to the names you use. There is one very small exception.
> > you are doing a commit to a URL with "tags" in the name, we will warn
> > that you might be committing to an incorrect location. We just copied
> > this feature from TortoiseSVN.
> I am new to Eclipse. Now it seems that project name (the folder name) is
> taken from the .project file and not from folder structure in SVN.
Correct. That is an Eclipse feature that we support. And a good one at
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Tue Apr 19 01:47:46 2005