False discovery of changed files, false content assigned to a directory, and destruction of sources files elsewhere.

Sorry, in subversion issue traker, the svn user that allows to assign a trouble to all developpers isn't working (wrong user it says).
My issue is the #3308, assigned to first single developper I saw in the list, but this developper might be unavailable.

Here is my issue:

From a new installation of Subversion and Tortoise 1.4.5, I have imported my
directories into subversion from Dev.

Dev
-- Project1
   -- src
   -- build
   -- classes
   -- build.xml

-- Project2
   -- src
   -- build
   -- classes
   -- build.xml

Then, I deleted with the Tortoise command build and classes because they have
build results inside. Later, after a compilation, these directory are
recreated, and I put them into ignore-list.

Projects are committed, and working directory refreshed by a complete update.

At this time a browse repository done with tortoise says something like this:

title/trunk/Dev
-- Project1
   -- src
   -- build.xml

-- Project2
   -- src
   -- build.xml

And this is what I want. If I go on my working directory, and right-click on
build or classes directory, it offers to remove them from ignore-list: I
understand that they are currently on ignore-list and this is perfect.

Few compilations laters, and this is a repeteable problem,
my classes directories are marked changed. But with theses rules:

1) If I try to see what is committeable from Dev (In case I would like to commit
every project) Nothing is said eligible to commit.

2) If I go to one of these classes directory Subversion says that files are
missing inside.
But the files said missen inside arent .class or such executable files. THEY
ARE SOURCE FILES.
I see this:
classes\sourcefile1.java missing
classes\sourcefile2.java missing

(and classes directories never had any java files in their lifecycle).

If I dare commit, these files will be deleted, but not from classes directory,
BUT from SRC directory.

3) classes directories are full of .svn files, that comes soon after they are
created. build directory isn't affected by this trouble and remain unchanged.
Received on Thu Nov 8 00:14:44 2007