You said, and I quote, "There is a class library in one branch but not in the other mixed with unversioned files that I can do nothing about."
I misread that statement to mean you had compiled output committed in one branch. You seem to be trying to point out that the class library is not compiled in the repository. The source code to the class library is. OK, that's fine. The point of fact is that there are "unversioned files that I can do nothing about." A few of us are pointing out the potential problems that occur when these unversioned files are important enough that they need to be kept around. You say you "can do nothing about" the fact that the unversioned files are important. I question whether there is really is nothing you can do. Sometimes tools gently point out that there are deficiencies elsewhere. We should not ignore them. I think the --force option is dangerous. Try it out but, in my opinion, you should not use it. I think Philip Martin's suggestion is a better solution. On 8/22/13 11:39 AM, John Maher wrote: > You digress. Not a single one of the compiled libraries lives within the > versioned directories. Please read the question before replying incorrectly. > It has nothing to do with code. It has nothing to do with the build. > Please ask for clarification if you do not understand. You gave a good > suggestion with the force option. Then you wandered off to completely > irrelevant ramblings. Should quit while you're ahead. > > -----Original Message----- > From: Edwin Castro [mailto:0ptikgh...@gmx.us] > Sent: Thursday, August 22, 2013 2:30 PM > To: users@subversion.apache.org > Subject: Re: Switching > > 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 > > > >
