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

Re: [Subclipse-users] Reattaching Projects Problem

From: Marco Maccaferri <macca_at_maccasoft.com>
Date: Tue, 02 Jun 2009 15:38:16 +0200

On 02/06/2009 14:39 Mark Phippard ha scritto:

> I'd guess your problem is just SVN client versions. For example, if
> your CLI checkout was using SVN 1.6 and you are using Subclipse 1.4.x
> (which uses SVN 1.5 client) then Subclipse cannot read the working
> copy and see it as such.

Don't know if it is related, but there is a scenario where the issue
occurs even when the versions are the same, I've spent half the day
yesterday trying to import a project that was connected to an svn
repository with the command line client.

Try this:

1. Copy a project to an svn controlled folder
2. From the command line add the project to svn (svn add projectdir)
3. From Eclipse import the existing project to the workspace. Answer no
to the dialog asking to add the project to svn (an issue already shows
with this message).

Note that the project does not look shared.

4. Try to Team -> Share -> SVN the project. Subclipse tells you that the
project appears to have svn metadata folders but it needs svn metadata
folders (?) to add to svn and it is going to delete them all. Ok, do
nothing, cancel the dialog.
5. Delete the project from Eclipse but keep the files on disk.
6. From the command line, commit the project.
7. Import the project again into Eclipse. The project still isn't shared
8. Do Team -> Share -> SVN and it detects that the project is already
connected to SVN!

Seems that there is something weird within the svn metadata detection
that goes beyond versions. If the project is added but not committed
subclipse doesn't detect the connection, after committing something
changes and subclipse detects that it is already connected.

Sometimes it isn't even necessary to do step 8 the projects are imported
already shared.

Subclipse: 1.4.2
Subversion: 1.5.4
Linux x86_64

In case you ask why I'm doing this, it is because I've created a new
project and wanted to commit the project and other related changes using
a single changeset. Yesterday I ended by committing the files from the
command line, hope to find a better solution for the next time.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-06-02 16:59:29 CEST

This is an archived mail posted to the Subclipse Users mailing list.

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