Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336692 - commit fails if a package was renamed/moved
Summary: commit fails if a package was renamed/moved
Status: CLOSED MOVED
Alias: None
Product: Subversive
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Igor Burilo CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-09 05:36 EST by Christian Schwarz CLA
Modified: 2023-02-13 10:56 EST (History)
3 users (show)

See Also:


Attachments
Commit Error Message (52.23 KB, image/png)
2011-02-09 05:40 EST, Christian Schwarz CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Schwarz CLA 2011-02-09 05:36:30 EST
Build Identifier: 20100917-0705

The commit fails after a package rename/move. Example :rename package "a.b.c" to "a.x.b.c".

I am using SVN Connector: Native JavaHL 1.6.6 r40053 (for SVN 1.6.6, win32 platform only)

Maybe this Bug is related to:
 * #251168 Refactoring Package does not delete original, but does add new Package to svn.
 * #243638 SVN: Rename of file fails when only difference is character case
 * #213991 Subversive SVN causing file renames to be reported as removal+addition in ResourceChangeEvents




Reproducible: Always

Steps to Reproduce:
1. update the project to get the latest version from the repository
2. rename package a.b.c to package a.b.x.c
3. try to commit
4. it fails with the following message (package & class name changed):

Some of selected resources were not committed.
Illegal target for the requested operation
svn: Commit failed (details follow):
svn: Entry for 'C:\XXX\workspace\test.project\src\a\b\c\Test.java' is marked as 'copied' but is not itself scheduled
for addition.  Perhaps you're committing a target that is
inside an unversioned (or not-yet-versioned) directory?
Comment 1 Christian Schwarz CLA 2011-02-09 05:40:19 EST
Created attachment 188577 [details]
Commit Error Message
Comment 2 Christian Schwarz CLA 2011-02-09 05:44:33 EST
I've testet it with a new project but was unable to reproduce it. It seems that the bug occures first time after serveral committs and/or updates or in larger projects.
Comment 3 Christian Schwarz CLA 2011-02-09 06:00:53 EST
Workaround to rename a.b.c to a.b.x.c:

1. update the project
2. rename the package from a.b.c to a.b.x
3. commit (after this the empty package a.b.c is left in the project and marked as deleted)
4. rename the package a.b.x to a.b.x.c
5. commit (after this the empty package a.b.c will disappear)
6. voila -> a.b.c is now a.b.x.c
Comment 4 Eclipse Webmaster CLA 2023-02-13 10:56:00 EST
This issue has been migrated to https://gitlab.eclipse.org/eclipse/subversive/subversive/-/issues/80.