On Friday 05 January 2007 7:12 pm, Mark Phippard wrote:
> 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.
After looking at how Subversion deals with externals on the command line (per
Manfred Klug's suggestion), I can see why this would be a problem for
Subclipse in & of itself. It's sad & frustrating. Any idea if there's
something in the works for revising how externals work? It's a powerful
feature, but seems to be just an afterthought of somebody that managed to get
their changes in before release time.
--
Best Regards,
Dan Falconer
"Head Geek",
AvSupport, Inc. (http://www.partslogistics.com)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Jan 8 15:44:31 2007