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

Re: [Subclipse-dev] WC-NC & checout at a level over project level

From: Mark Phippard <markphip_at_gmail.com>
Date: Thu, 15 Dec 2011 07:44:37 -0500

There are other people that use a similar structure. There is no
reason it should not work. Subclipse does not use the presence of the
.svn folder to determine that the project is part of SVN.

I would look for other errors in the log.

On Wed, Dec 14, 2011 at 7:09 PM, Matthias Ludwig
<matthias-ludwig_at_gmx.net> wrote:
> I have a question concerning subclipse > 1.8
> We commit / checkout projects on eclipse workspace level like this:
> eclipse-workspace ( = checkout dir)
>   .svn
>   project1
>   project2
>   svn-external-project1
>   svn-external-project2
> This gives us the possibility to assemble the components of a customer project. With svn-externals we include general components.
> Because of this aproach the project folder is not the root svn checkout root folder. For WC-NC this means the .svn working copy database is on a higher level than the project folder.
> And here is my question:
> I observed that subclipse 1.8 does not recognize that the project is part of svn working copy. Context menue does not show team provider items. I suppose that this has someting to do with WC-NG format. With earlier versions erverything worked.
> Did I miss something? Is there any way to configure subclipse to regognize the working copy?
> Thank you very much for any help.
> ------------------------------------------------------
> http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1043&dsMessageId=2893369
> To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_subclipse.tigris.org].

Mark Phippard
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_subclipse.tigris.org].
Received on 2011-12-15 13:44:47 CET

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