On 8/22/13 10:54 AM, John Maher wrote:
> This happens even if you do not do a build. There is a class library in one branch but not the other mixed with unversioned files that I can do nothing about.
Statements like this make me believe that build system is broken. I
would expect the svn switch like problems on nearly any SCM you use that
has the ability to switch a single working copy (or workspace, client,
what-have-you) between branches. My knee jerk reaction in situations
like this is to fix the build system.
Are you sure there is nothing you can do? Perhaps you can suggests a
simple fix like moving the versioned class library to a location that is
always versioned. For example, instead of referencing a class library
that lives in a bin/ directory it is better to keep the class library in
a lib/ directory instead. Build output goes in the unversioned bin/
directory and versioned resources go in the lib/ directory.
Edwin G. Castro
Received on 2013-08-22 20:30:44 CEST
This is an archived mail posted to the Subversion Users