On 7/16/07, Erich.Buri@swisscom.com <Erich.Buri@swisscom.com> wrote:
> I just wanted to do a „Share Project…" on an existing project in eclipse to
> import it into a subversion repository. I'm using the
> one-repository-per-project approach. There for the folder structure is just:
> now, I would like subclipse to import all files from the project into the
> trunk/ directory. But subclipse insists on creating a new directory in the
> repository! I can choose between "Use project name as folder" and "Use
> specified folder name". So I browse for the trunk/ folder to tell subclipse
> so import all files directly under trunk. Then I hit next and enter a
> commit-message. After hitting Finish, Subclipse says: "Folder trunk/ already
> exists, you must specify a folder name that does not already exist " Why??
> IMHO, that's a bug.
Because if there is content inside trunk, the Subversion API's do not
provide any facility for handling that. So we require you to share to
a non-existant folder. In your case you could delete trunk so that
the share process can create it.
> When I do an import from the command line with:
> svn import project/
> Everything works as expected.
Well, you can also do this with Subclipse, but then you would have to
delete your project and checkout again.
> Why does subclipse require a special folder? Could that "feature" be
No one is denying that a human being that knows that they are doing
and understands Subversion ought to be able to do this stuff. We are
just coding safely and in within the boundaries of what the API's
available give us.
As I mentioned earlier today on this exact same issue, Subversion 1.5
has improved the checkout API such that we can possibly remove this
restriction. 1.5 has not been released yet so this would all be in
some future Subclipse release.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Jul 16 17:17:49 2007