On Wed, Mar 7, 2012 at 6:56 AM, jack nimble <jackbenimble...@gmail.com> wrote:
> 'm trying to create a new entry in subversion for development. This is based
> on a project which already exist in subversion. I don't want to have it
> based on that version, because that's for reference only and can't be
> changed.
Can you create a new branch? That way, you can check out and change
the branch without changing the "reference" copy.
>
> I tried to export it using subclipse in sts/eclipse. However, when I import
> the top level project into sts/eclipse, the project structure isn't
> preserved.
If you are "exporting" the project and not "checking out" the project,
you don't have a working copy.
>
> The sts/eclipse project structure is preserved when I do a checkout. So I
> checked out the project to a different directory path. Then, using cywin's
> command line, I recursively removed all the .svn entries from the project
> with a "find.-name".svn"-execrm-rf{} \;"
Those ".svn" directories give Subversion the information it needs in
order to know that this is a working copy. Remove them, and you no
longer have a working copy.
Make a branch. In Subversion, it's easy to do. Do a "svn cp" to the
"branches" directory and use that. That way, you can make your changes
without changing the "reference". If the "reference" changes, and you
need those changes, you can merge them into your copy. If you decide
that these changes should go back into the "reference", you can merge
your changes back into the "reference". This is what branching is for.
--
David Weintraub
qazw...@gmail.com
