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. More inline.
On Tue, Jun 2, 2009 at 6:56 AM, Hoffmann, Niels<n.hoffmann_at_bgbm.org> wrote:
> I am a little bit confused about subclipse behaviour concerning existing
> projects that get reimported into eclipse and then should be reshared via
> subclipse.
>
> Here is the scenario:
>
> 1.
> I am checking out a folder from a subversion repository via svn CLI. The
> folder contains multiple eclipse projects. So I end up with a directory
> structure like this:
>
> folder_from_subversion/
> .svn/
> eclipse_project_1/
> eclipse_project_2/
> eclipse_project_3/
>
> 2.
> I then use the Eclipse Import Wizard to import "Existing projects into
> workspace" and choose the projects and am now able to work with them. From
> Eclipses side everything looks fine.
At this point you already are showing the problem. If Subclipse could
read the WC the projects would have been automatically connected when
you imported them. You should not need to do Team > Share.
> The reason I am doing it like this and not import every project via
> "Import->SVN->Checkout Projects From SVN" is, that I also need other
> metadata files managed by subversion in the directory above the eclipse
> projects.
Sure, this is extremely common use-case. Even documented in the help.
> 3.
> As I want to commit changes I made to the code, I obviously want to have the
> projects connected to the subversion repository they were initially checked
> out from. As far as I can see, you are supposed to do this via "Team->Share
> Project"
>
> And then this happens:
> The "Share Project with SVN Repository" Wizard warns me that: "Project
> contains Subversion metadata folder" which I thought is well as I want to
> reconnect it to the repository and merely need subclipse to recognize any
> existing subversion configurations.
> The Wizard also warns me that it is going to delete the .svn folders and
> then states something which I do not understand. "In order for Subclipse to
> automatically reconnect a project to a repository, the project root folder
> needs to contain a Subversion metadata folder. Most likely it doesn't, or
> you would not see this message."
We could possibly enhance this message to cover your scenario.
Basically, we tried to read the WC using an API. This failed because
it does not know how to read the newer format. As far as we know, it
just is not a WC. We then have a check for folders named ".svn".
Rather than just delete them (destroy your WC, we warn you). The most
common cause in the past has been that some sub-folders in your
project are from SVN, but not the project root folder.
> So what is the "project root folder"? Is it the folder where my eclipse
> projects reside in a.k.a the folder I checked out from the repository? Well,
> that folder does contain subversion metadata?
No, the "eclipse_projec1" folder in your example.
> What am I doing wrong here?
See: http://subclipse.tigris.org/wiki/JavaHL
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2358764
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-06-02 17:02:28 CEST