On 9/17/07, Mehdi Rabah <mehdi.rabah@gmail.com> wrote:
> > > Thanks for your answer, I didn't know about svn:externals, and it
> > > worked perfectly.
> > >
> > > I edited the svn:external property on a folder with subclipse and it
> > > was detected as an external folder. But when I tried to update it
> > > didn't retrieve the code from this external repository (update !=
> > > checkout). I had to make the checkout from the shell and then it
> > > worked (I could update and commit).
> > >
> > > What I mean is that subclipse miss a feature to retrieve data from an
> > > external project when a folder was detected as external. Or I missed
> > > something :)
> >
> > Did you commit the svn:externals property change before doing this?
> > Subclipse certainly pulls down the externals content automatically.
> > Well, technically Subversion does it. We just run the svn update API.
> >
> > I usually just do update on my top-level project folder and it does everything.
> >
>
> Ok that was the problem. But I still have other problems, here they
> are, just FYI.
>
> When I delete the external folder, subclipse tell me "svn: 'MyApps' is
> not under version control". (of course it's not since it's external,
> but I still want to delete it)
externals are no different than if you checked them out. They are
under version control and managed just like anything else. You can
make changes and commit etc.. If you want to get rid of them you need
to edit the property and update. Then delete the folder. Subversion
is conservative and will not delete them for you.
> Also, if I set svn:externals for the folder which is on my repository
> I have "svn: Working copy '/myproject/ExternalCode' locked; try
> performing 'cleanup'". Of course cleanup didn't solve the problem. I
> have to set svn:external for a subfolder, like
> /myproject/ExternalCode/subfolder for it work.
That is usually an indication that a a .svn folder has been removed.
svn:externals does allow you to set multiple-level folders like this.
I would discourage it if possible. In your example, I would add a
folder named ExternalCode that contains the svn:externals properties
on it.
> I don't know if it's normal but If they are persistent I'll fill a bug report.
Send it to the list first. In most cases the issues are going to be
in Subversion. So we would want to discuss if it was possible to
workaround whatever the underlying issue was.
--
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 Mon Sep 17 16:08:36 2007