> > I'm giving that a try. I created new remote folders following the
> > guidelines from the SVN book: <project-name>, trunk, branches and
> > tags. Now, when issuing the Team -> Share Project command,
> do I want
> > to
> > A) use an existing repository location and specify the URL
> in the "Use
> > specified module name" field of the Enter Module Name step
> > B) create a new repository location, specifying the URL as
> > <existing-repository-location>/<project-name>/trunk
> > Option A doesn't seem right. Option B seems more likely
> what I want
> > to
> > yet the terminology is confusing: I already have a "repository
> location" in
> > the Eclipse sense; why would I want to "create" another one? Please
> I think you are right, I got a bit confused there. The
> feature used to
> now work at all, but does in the newer Eclipse 3 builds
> (although not the
> most current one). However, I do not think it can share to a
> "deep URL"
> for lack of a better description.
> What I have always done is use Tortoise to create the initial
> import, and
> then use Subclipse to check back out.
> Here is a message and thread about this recently:
Thanks for the clarification. I've been using this technique with the
command-line/TortoiseSVN and subclipse, too. I'll keep using it for now.
Received on Tue Aug 17 06:11:04 2004