I have a similar problem. The work around I tried was to check in empty
folders - aka the ones that are getting marked unversioned. It fixes the
behavior some of the time, but not all of the time. I'm not sure how to
proceed any further since I can't reproduce the remaining behavior. I've
just been tolerating it - I blow the folder away and replace with latest
from time to time.
Katherine Hale
Software and Web Applications Developer
Sogeti USA
________________________________
From: Dan Falconer [mailto:crazedsanity.com_at_gmail.com]
Sent: Monday, September 08, 2008 1:20 PM
To: users_at_subclipse.tigris.org
Subject: [Subclipse-users] Externals folder becomes unrevisioned
First, let me say that I've been a subclipse user many many years and I
have been very happy with it. I have recommended it multiple times over
competing PHP IDE's.
Also, I am not a member of this list (yet), so please CC me with your
responses.
THE PROBLEM:
When I commit anything in my base folder, then update, one of my
externals becomes marked as unversioned. I have to delete the folder
and run an update on the base folder again, and the externals file comes
back.
VERSION INFORMATION
ECLIPSE::: Version: 3.3.2 Build id: M20080221-1800
Subclipse::: 1.4.4
SVNKit Client Adapter::: 1.5.1.1 <http://1.5.1.1/>
SVNKit Library::: 1.2.0.4820
THE LAYOUT:
/sitefolder/
bin/
...
lib/
...
eternals/
cs-arrayToPath
cs-content
cs-phpxml
...
public_html/
...
The svn:externals property is set on /sitefolder/lib/ as:
externals/cs-content
https://cs-content.svn.sourceforge.net/svnroot/cs-content/trunk/0.10
externals/cs-phpxml
https://cs-phpxml.svn.sourceforge.net/svnroot/cs-phpxml/trunk
externals/cs-arrayToPath
https://cs-arraytopath.svn.sourceforge.net/svnroot/cs-arraytopath/trunk
The folder that constantly gets marked as unversioned is the
cs-arrayToPath definition (last in the property, first in the directory
structure). As stated previously, I delete the folder & run an update
to get it back.
WHAT I'VE TRIED:::
1. In an attempt to troubleshoot the problem, I re-arranged the
contents of the svn:externals property so the cs-arrayToPath folder is
now the first in the list... NO EFFECT.
2. I noticed an "svn:ignore" property set on the externals folder
(value was "cs-content"), so I removed; this set ALL externals as
unversioned... deleted folders, ran update, externals good again.
3. Removed "cs-arrayToPath" from externals definition & committed:
all externals showed properly (cs-arrayToPath still showed as
versioned...); ran update, and now cs-arrayToPath AND cs-content show as
unversioned... deleted both folders, ran update, cs-content came back.
4. With cs-arrayToPath still removed from svn:externals, made
another commit, then updated base folder: now the cs-content folder
shows as unversioned!
I would certainly appreciate any help I can get on the matter. If more
information is needed, please let me know! Thanks!
Received on 2008-09-09 17:00:28 CEST