An "external" project is not always logically and physically separate
from the main project. Where I work, there are several "external"
references which are used by different applications. All of these
applications are released together as a group from a higher-level
folder, but they are not all part of the same lower-level project tree.
Since some of the dlls are shared, we use the "external" references.
Quite possibly, a better arrangement of the subversion folders would
change this. But, the system works, and reorganizing the projects and
folders would be quite a bit of work.
Maybe we could add a new property to parent folders, specifying
automatic inclusion of specific external references. That way people
could actually get the requested behavior, but the default would be to
remain as it is.
(Y'know, I thought that our project layout actually did auto-include our
"external" references. Does this behavior change when the referenced
projects are contained in the svn server?)
John
-----Original Message-----
From: Donald H Locker [mailto:donald.locker_at_ptmelec.com]
Sent: Monday, August 04, 2008 6:26 AM
To: users_at_tortoisesvn.tigris.org
Subject: Re: Recursively commiting files placed in svn-externals
projects
And, I would submit, committing externals from within a different
working
copy would be the wrong thing to do.
An external project is a logically and physically separate entity from
the
main project. If a developer makes changes in the external project
while
working on the main project, those changes need to be vetted differently
than changes in the main project. By the same token, a developer
working on
the external project is not working on the main project and needs to
deal
with the external project differently.
Donald.
Andy Levy wrote:
> On Mon, Aug 4, 2008 at 06:13, Gabriel <gabrielvdk_at_gmail.com> wrote:
>> Hi,
>>
>> We use the svn-exertnals property quite a lot to include libraries
and
>> frameworks into our seperate projects. This all works great. But I
>> think one think you be even easier. The problem is when you commit
the
>> root folder of the project everything is commited except for files
and
>> folders in the svn-external folders. You need to seperately do this
>> for each external project (in our case: the data project, framework
>> projects & javascript framework).
>
> Externals actually create a SECOND working copy inside the parent WC.
> They have to be committed separately because if the external comes
> from a different repository, it's impossible for the commit to be
> processed as a single transaction.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
> For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
>
--
Donald H Locker
PTM Electronics, Inc
734 426 9010
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-08-04 15:20:28 CEST