You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by J Hicks <jo...@att.net> on 2008/04/25 15:01:15 UTC
Nested projects and changing folder names
Hello Dev,
1st issue: nested related projects.
Many of my projects are set up like:
Mainproject
/src
/bin
/images
/help
/helperproject
/src
/bin
/doc
/ship
/updater
/src
/bin
/doc
/images
Now I create an empty structure for this in svn,
I go to checkout the project OVER my existing real code and svn gives
me this error saying folder already exists /images.
Is there a problem with this structure? Do I have to check in the
updater or helperproject as separate projects? That would certainly be
inconvenient. the overall project is a single entity and difficult to
separate.
I'm fairly new to svn and may have to change the way I'm working
(which has already changed due to svn). Right now I set up the set of
folders for a new project, start a new project in my ide and save it
to the new structure, then continue developing. As I need
sub-projects I add the new sub folders, then create the new project
in those folders as part of the same project group. When I'm ready
for the first release, I attempt to get it all into svn at that point
except I'm having a difficult time getting it into svn. (I'm actually
using tortoisesvn.)
Do I have to check out the whole project into a new folder, then
copy the files from my working project into those and then check it
all back in? That would be a pain as well.
Should I just make a new project folder in svn and
trunk/branches/tags folders with no sub folders and then check that
out into my project, and then commit my project back in to the trunk
folder?
the trouble is I'm a single developer and I only do the svn
interaction when I'm done with something or have to stop or switch
projects for a while. That might be a week or two between steps.
2. I started out with maybe a sub-project folder name of
xyzUpdaterProject, then I change it later to xyzUpdater to shorten
the path. I get all kinds of problems with svn on this. It keeps
saying the xyzupdaterProject folder is missing. I end up changing
things often in development. I thought I could just rename the folder
(or filename) in svn and it would handle it but I must be wrong.
Best regards,
Joe Hicks
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Nested projects and changing folder names
Posted by Erik Huelsmann <eh...@gmail.com>.
Please mail usage questions to users@, this list is not about
development *with* subversion, but development *of* Subversion (ie.
the program itself).
Thanks for your consideration.
Bye,
Erik.
On Fri, Apr 25, 2008 at 5:01 PM, J Hicks <jo...@att.net> wrote:
> Hello Dev,
>
> 1st issue: nested related projects.
>
> Many of my projects are set up like:
>
> Mainproject
> /src
> /bin
> /images
> /help
> /helperproject
> /src
> /bin
> /doc
> /ship
> /updater
> /src
> /bin
> /doc
> /images
>
> Now I create an empty structure for this in svn,
>
> I go to checkout the project OVER my existing real code and svn gives
> me this error saying folder already exists /images.
>
> Is there a problem with this structure? Do I have to check in the
> updater or helperproject as separate projects? That would certainly be
> inconvenient. the overall project is a single entity and difficult to
> separate.
>
> I'm fairly new to svn and may have to change the way I'm working
> (which has already changed due to svn). Right now I set up the set of
> folders for a new project, start a new project in my ide and save it
> to the new structure, then continue developing. As I need
> sub-projects I add the new sub folders, then create the new project
> in those folders as part of the same project group. When I'm ready
> for the first release, I attempt to get it all into svn at that point
> except I'm having a difficult time getting it into svn. (I'm actually
> using tortoisesvn.)
>
> Do I have to check out the whole project into a new folder, then
> copy the files from my working project into those and then check it
> all back in? That would be a pain as well.
>
> Should I just make a new project folder in svn and
> trunk/branches/tags folders with no sub folders and then check that
> out into my project, and then commit my project back in to the trunk
> folder?
>
> the trouble is I'm a single developer and I only do the svn
> interaction when I'm done with something or have to stop or switch
> projects for a while. That might be a week or two between steps.
>
> 2. I started out with maybe a sub-project folder name of
> xyzUpdaterProject, then I change it later to xyzUpdater to shorten
> the path. I get all kinds of problems with svn on this. It keeps
> saying the xyzupdaterProject folder is missing. I end up changing
> things often in development. I thought I could just rename the folder
> (or filename) in svn and it would handle it but I must be wrong.
>
> Best regards,
> Joe Hicks
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org