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

RE: [Subclipse-users] Issue with Subeclipse plugin behaviour

From: Pervinder Sudan <pervinder_at_vendavo.com>
Date: 2007-09-11 02:09:02 CEST

-----Original Message-----
From: Mark Phippard [mailto:markphip@gmail.com]
Sent: Thursday, September 06, 2007 9:19 AM
To: users@subclipse.tigris.org
Cc: Pervinder Sudan
Subject: Re: [Subclipse-users] Issue with Subeclipse plugin behaviour


On 9/6/07, Pervinder Sudan <pervinder@vendavo.com> wrote:

> We have been working on the migration to Subversion from CVS and we

> through the migration stuff successfully but now I am running into a

> problem in Eclipse which was not there in CVS-Eclipse combination. Our

> is organized such that we need to checkout a module with in the module

> then compile. Eg is

> Say we have Test/src Test/meta and other folders and then we have

> module Client/src ... that needs to be checked out into the Test/meta

> that final hierarchy looks somewhat like this Test/meta/Client/src. It

> worked fine in CVS-Eclipse combination as we were able to browse /
history /

> diff and other CVS operations on both the Test and Client Modules but
now in

> the SVN-Eclipse combination It doesn't read the Client modules history

> we are running problem. Can someone just explain this ? It is a

> for the developers.


- Subversion has a lot stricter rules on the layout of the "working

- copy". The Subversion feature that lets you do something like this is

- svn:externals. I would suggest you look at that feature to provide




Mark Phippard
I have tried that and it works fine but I have n number of clients and
different teams working on different clients with restricted access to
the respective clients. I can not set the property for n clients on that
Received on Tue Sep 11 02:08:32 2007

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.