Bugzilla – Full Text Bug Listing
| Summary: | TM: Lose target'ness if project renamed | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Kevin McGuire <Kevin_McGuire> |
| Component: | Resources | Assignee: | DJ Houghton <dj.houghton> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Michael.Valenta |
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 17944 | ||
| Bug Blocks: | |||
|
Description
Kevin McGuire
This is tricky. It looks like the sync info is not maintained after project deletion. Therefore, there is no window of opportunity to copy the sync info from the old project to the new one. In pre-delete, the new project does not exist, so we cannot copy the the sync info to it. In post delete, the sync info is no longer on the old project so it is lost. We could remember the target provider info for the brief time between these two but this is impractical for our synchronized providers as they have sync info on each resource. Possible solutions include: 1. Ask core to more sync info on project moves. This could gaurantee success. 2. Investigate the possibility of using the move/delete hook. I think we could only do this if there was no Repository Provider or the provider returned false (indicating default behavior). In these cases, we could possibly provide a custom project delete that supported the transfere of sync info. Re #2: you only get move/delete if you are a repository provider, which we are not. I guess this didn't work in 1.0 with cvs projects either? Actually, I think there was a time where you couldn't rename projects anyway. Moving to Core to investigate moving of sync info on rename. |