| Summary: | commit fails if a package was renamed/moved | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] Subversive | Reporter: | Christian Schwarz <chriss.dev> | ||||
| Component: | Core | Assignee: | Igor Burilo <igor.burilo> | ||||
| Status: | CLOSED MOVED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | a.gurov, chriss.dev, vladnc | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Christian Schwarz
Created attachment 188577 [details]
Commit Error Message
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. 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 This issue has been migrated to https://gitlab.eclipse.org/eclipse/subversive/subversive/-/issues/80. |