Hi,
I believe this is a bug. I'm using subversion 1.2.3 on Windows XP and
subclipse 0.9.34 in Eclipse 3.1. Here are the steps to reproduce the
problem:
1. Rename an existing file say Foo.java to Bar.java in Eclipse.
2. Create a new file Foo.java in Eclipse.
3. Synchronize and commit. The console output is:
move C:/workspace/workflow/src/mo/org/cpttm/workflow/Foo.java
C:/workspace/workflow/src/mo/org/cpttm/workflow/Bar.java
A C:/workspace/workflow/src/mo/org/cpttm/workflow/Bar.java
D C:/workspace/workflow/src/mo/org/cpttm/workflow/Foo.java
commit -m "Kent" C:/workspace/workflow
Adding workspace/workflow/src/mo/org/cpttm/workflow/Bar.java
Deleting workspace/workflow/src/mo/org/cpttm/workflow/Foo.java
Transmitting file data ...
Committed revision 3.
4. Inspect the repository in the subversion exploring perspective, only
Bar.java is there, but Foo.java is not. The expected result is that
both Bar.java and Foo.java should be there.
5. The icon of Foo.java has a brown-color cross, indicating something
is wrong, but there is no error or warning in the Problems window in
Eclipse.
6. Perform a synchronize. Foo.java is listed as an outgoing change in
the Synchronize window, but when committing, only the /workflow folder
is listed as a resource to be committed, not Foo.java. Committing it
will seem to suceed but Foo.java is not committed. The console output
is:
commit -m "Kent" C:/workspace/workflow
which confirms that nothing is done.
7. Go back to the Java perspective, Foo.java is not longer marked
with a cross, but with a question mark, indicating that it isn't
version-controlled.
Any idea?
Received on Sat Oct 22 21:25:00 2005