> -----Ursprüngliche Nachricht-----
> Von: "Mark Phippard" <markphip@gmail.com>
> Gesendet: 06.01.07 02:10:38
> An: users@subclipse.tigris.org
> Betreff: Re: [Subclipse-users] Bug with externals decorator?
On 1/5/07, Dan Falconer <lists_subversion_users@avsupport.com> wrote:
> I've got a repository that runs our web application, and I've got some
> open-source PHP libraries that I use. To keep them up-to-date, I have
> svn:externals setup to retrieve each of them..... Here's the relevant
>
> portion of the directory structure:
> /lib/externals/
> cs-arrayToPath/
> cs-phpxml/
>
> The "externals" directory in lib is under version control. On "/lib", I've
>
> got the svn:externals definition:
>
> externals/cs-arrayToPath
> https://cs-arraytopath.svn.sourceforge.net/svnroot/cs-arraytopath/trunk
>
> externals/cs-phpxml
> https://cs-phpxml.svn.sourceforge.net/svnroot/cs-phpxml/trunk
>
> I've set the "externals" dir to ignore everything ("*" for "svn:ignore"), and
>
> the first time (or possibly several times), the decoration that shows the two
> folders as external appears. When I perform an update on the root of the
> project (Team->update), the decoration disappears. If I remove the
>
> "svn:ignore" property on externals, the decoration is back... but the next
> time I open Eclipse, or by performing an update (or even refresh, I believe),
> the decoration disappears.
>
> I haven't tried setting the "svn:externals" setting directly on the
>
> "externals" folder for this project, though I believe that caused issues with
> another project (with a different version of Eclipse/Subclipse). Any help
> would be much appreciated: without that decoration, I'll forget they're
>
> external, and the other devs will have no clue.
>
> The best I can say is that I do not think that svn:ignore is the main issue here.
> I think almost everyone sees this behavior. I do not know 100% what causes it but I think what it boils down to is that
> Subversion is inconsistent in how it reports externals depending on which API you use and from where. This is then
> complicated by our own cache and which version it has cached. We have a lot of workarounds in different places to handle
> some of these inconsistencies but apparently not all of the places.
Yes, it is an inconsistency in subversion, but AFAIK it works as designed.
- If you look at the status of lib, both folders are external.
- If you look at the status of externals, both folders are unversioned.
- If you look at the status of the external folders, they appear as normal svn folders.
Depending on the folder, which subclipse has used for the last status query, you get one
of the three icons (external / unversioned / versioned).
The svn API is useless to establish a reliable display of externals.
Manfred
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sun Jan 7 11:08:37 2007