Community
Participate
Working Groups
0. To test this, I added a new repository to the server, retrial, and on the command line added a password for it. 1. In Eclipse, Create Java Project named retrail (a typo but there it is). New/Class to add classes FirstClass and SecondClass to package foo. 2. Select project in packages view, Team/Share Project... to add retrail project to retrial repository. Clicked the Create a new repository button and entered info, otherwise defaults all the way. 3. In Synchronize view, right-clicked on top level and did Add then Commit. 4. In server, verified that files are committed. Snapshot of repository at that point attached. 5. Back in packages view, New/Package bar. 6. In packages view, drag FirstClass to bar package. Verify package statement added. 7. In editor, double-click SecondClass and Refactor/Rename... Change name to RenamedSecondClass. 8. In packages view, right-click Team/Synchronize with Repository... 9. Bug: Synchronize fails with two errors. Alert says error in .../foo/FirstClass and .../foo/SecondClass. Project as of 9 and .log attached (or will be shortly).
Created attachment 1328 [details] Zipped repository and project folders, .log file.
Bob, this seems like a dupe of 19704 which you also just recently logged. Marking it duplicate, reopen with explanation if its actually a different bug somehow. *** This bug has been marked as a duplicate of 19704 ***
Bug 19704 describes a case where the repository would up containing both copies of files that had been moved or renamed. When I tried to reproduce it with a similiar case I wound up describing a different problem, which someone (you?) noted. So I decided to file the other problem separately. Unfortunately, I didn't get that far. This bug is simply about being unable to synchronize after move and rename.
