Thanks Mark and Lira. My situation is basically the same as yours Lira.
Mark, I'm not sure I explained myself properly, since none of the
folders are unversioned, they all have .svn directories, and the
svn:externals property on the root is reported correctly by subclipse.
For simplicity's sake, imagine my project looks like this:
MyProject [trunk/MyProject]
/Folder1 [trunk/MyProject/Folder1]
/Folder1a [trunk/thirdparty/Folder1a]
Rather than setting the external on Folder1, it is set on MyProject like so:
Folder1/Folder1a http://svn/trunk/thirdparty/Folder1a
The command line client handles this OK, it recognises that Folder1a is
an external whether I run commits/updates/reverts etc from the context
of Folder1 or MyProject. Whereas subclipse shows the unversioned icon on
Folder1a and if I try to run any commits/updates/reverts etc on either
MyProject or Folder1, it treats Folder1a as if it was unversioned. I
realise I can get around this by putting the property directly on
Folder1, but unfortunately this isn't an option for me.
So it seems that Subclipse doesn't yet handle this case, no worries.
Since the command line client seems to handle this situation, it would
be great for subclipse to be able to handle this in a future version.
Anyway, keep up the good work and thanks for building a great tool.
Cheers,
Tom
Lira Olavo wrote:
> Here is my thread about the same problem in subversion user list:
>
> =====================================================================
> =====================================================================
>
> On Dec 18, 2006, at 12:18, LIRA Olavo wrote:
>
>
>>> I'm not sure that I realy understand.
>>> Your question seems to be "Can I have two directories with the same
>>> name at the same place ?".
>>> What would you like subversion to do exactly when you checkout your
>>> project A ?
>>>
>>> EEBXXX_YYYZZZ (From Project A)
>>> Dev (From Project A)
>>> ??? (From Project B svn:externals), it can not be also Dev...
>>>
>> Hi Christophe,
>>
>> Sorry if I didn't explain may self correctly. Here is another
>> try:
>>
>> EEBXXX_YYYZZZ (From Project A)
>> Dev/
>> Tools (From Project A)
>> Applet (From Project B svn:externals)
>> OS (From Project B svn:externals)
>> Ext (From Project A)
>> Plugin (From Project C svn:externals)
>>
>> So in order to have the picture above my svn:externals should be:
>>
>> Dev/ https://svnrepository/ProjectB/Applet
>> Dev/ https://svnrepository/ProjectB/OS Dev/
>> https://svnrepository/ProjectC/Plugin
>>
>> But then I have the error I've shown you because I Project A has
>>
>
>
>> already the Dev directory.
>>
>> If svn:externals cannot handle this, do you know another way to
>>
> link
>
>> directories from different projects?
>>
>
> svn:externals can handle this just fine. But you need to set
> svn:externals on the Dev directory of Project A then, not its parent
> directory, and the contents of the svn:externals property on the Dev
> directory should be as follows:
>
> Applet https://svnrepository/ProjectB/Applet
> OS https://svnrepository/ProjectB/OS
> Plugin https://svnrepository/ProjectC/Plugin
>
> =====================================================================
> =====================================================================
>
>
> I hope this can help you,
>
> Olavo Lira
>
> -----Original Message-----
> From: Mark Phippard [mailto:markphip@gmail.com]
> Sent: Tuesday, February 13, 2007 6:19 AM
> To: users@subclipse.tigris.org
> Subject: Re: [Subclipse-users] Problems with externals
>
> On 2/12/07, Tom Walter <walter.tom@gmail.com> wrote:
>
>> Hi all,
>>
>> Not sure if this is something wrong with my setup or a subclipse
>>
> issue.
>
>> When I have externals set directly on the directory to which they
>>
> apply,
>
>> it seems to work fine.
>>
>> But when I have an external set at the root level which applies to a
>> directory deeper in the heirarchy, subclipse displays those
>>
> directories
>
>> as 'unversioned' and when I go to do commits/reverts etc, handles them
>> as if they were unversioned files.
>>
>> I'm using eclipse 3.2.0 and subclipse 1.1.10.
>>
>
> That is the normal behavior. When you use externals like this, the
> intermediate folders are unversioned (they do not have .svn folder).
> You just have to know to try to not perform any operations on those
> folders. There was a thread about this maybe 4-6 weeks ago if you
> want to try to find it.
>
>
Received on Fri Feb 16 01:14:17 2007