On 9/17/07, Mark Phippard <markphip@gmail.com> wrote:
> On 9/17/07, Mehdi Rabah <mehdi.rabah@gmail.com> wrote:
> > On 9/12/07, Mark Phippard <markphip@gmail.com> wrote:
> > > On 9/12/07, Mehdi Rabah <mehdi.rabah@gmail.com> wrote:
> > > > Thanks for this software which I can't live without anymore.
> > > >
> > > > I wanted to ask you if there's a way to checkout a project as a folder
> > > > of another project ?
> > > >
> > > > For now I use the shell, but it's not working really well:
> > > >
> > > > **checkout project someLib with subclipse**
> > > > cd someLib
> > > > svn co file:///myCode
> > > >
> > > > resulting tree:
> > > >
> > > > someLib
> > > > +someLibSrc
> > > > +myCode
> > > > ++myApps
> > > >
> > > > when I update this project, the "myCode" project is detected as
> > > > unversionned but I can still update the myApps folder (and that's what
> > > > I want)
> > > >
> > > > It is possible to see this "Checkout as Folder" feature in subclipse
> > > > in the future ?
> > >
> > > I do not foresee it happening. The connection with the Eclipse
> > > Project and a Team Provider happens at the project level. Our code
> > > makes the assumption that the project itself is connected to
> > > Subversion. In your case, it sounds like that might be true. If so,
> > > then you should look into using the svn:externals feature in this
> > > project, which offers you a "native Subversion" way to pull in code
> > > from another project.
> > >
> >
> >
> > 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)
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.
I don't know if it's normal but If they are persistent I'll fill a bug report.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Sep 17 15:59:14 2007