On 9/6/07, shumisha <shumisha@gmail.com> wrote:
> Let me first thank developers and supporters of the great project. I am only
> starting to use it, but it has great promises of improvement in the way I
> work (on my GPL software).
> I have found startup very easy. I did ran into questions about the best
> organisation of my local projects and SVN repository. Search on this forum
> only yielded very old and/or not exactly on topic thread, so here it goes :
>
> - I develop extensions for the Joomla CMS. This means PHP/MYSQL and a Joomla
> provided SVN server
> - All of this works happily together :
> PHPEclipse+xDebug+Subclipse+Joomlacode.org (Joomla extensions development
> site)
> - the various files for my comp are stored in SVN repo. The comp is made of
> a few files, that once installed within Joomla, are located in 3 directories
> : let's say /admin/my_comp, /components/my_comp and /modules
> - For development and testing purpose, I have on my local machine several
> instances of Joomla setup. Each instance correspond to a common user setup.
> Each setup is made of many directories. Once installed, the various parts
> of my comp resides in Joomla own directories /test_setup_1/admin/my_comp,
> /test_setup_1/components/my_comp and /test_setup_1/modules
> Needless to say, in /test_setup_1/admin/, there are many other extensions
> that Joomla needs to work, or other extensions I want to have to test for
> compatibility
>
> - Now I thought I would be able to simply checkout a working copy from SVN
> into the /test_setup_1/ Eclipse project, in order to get a fully working
> Joomla install with my extensions
>
> - but what happens (as it should, this is not a bug), Subclipse actually
> delete the content of /test_setup_1/admin/ (and /test_setup_1/components)
> when doing the checkout. It removes anything that is not in SVN, all
> "unversionned" files and directories.
>
> I can think of another SVN repos organisation that would work around this,
> but it would be much less efficient and require a bit of work from me at
> every checkout and commit.
>
> So the final question : Is there a way to tell Subclipse NOT to delete
> unversionned files when doing the checkout in an existing project, to
> preserve my working environnement ? am I completely missing something ? how
> do people developping extensions to an existing software organize themselves
No. In the current code we have to delete anything that exists
locally. This is because the Subversion Checkout operation will abort
if it runs into anything that exists locally. Subversion 1.5 has an
option to handle this better and we are exploring how to use that to
handle other situations like this.
I think one thing a lot of people do today is just move these other
files out of the way, do the checkout, and then put them back.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Sep 6 13:26:09 2007