| Summary: | Don't offer to do a deep copy/move of linked resources | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Knut Radloff <knut_radloff> |
| Component: | UI | Assignee: | Adam Kiezun <akiezun> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P2 | CC: | akiezun |
| Version: | 2.0 | ||
| Target Milestone: | 2.1 RC1 | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
Knut Radloff
couldn't you have told us a week ago? <g> i mean, before i implemented it :) Knut, what is the deeper reason for removing this feature? It started with a debate about the wording of the deep copy prompt and concluded that the linked resources UI would be simpler if we didn't support deep copy/move in the first place. We considered a separate action to convert a linked resource to a regular resource (and thus initiating a deep copy). We decided that is not necessary because you can manually create a deep copy of a linked resource by copying the contents. See the quote in bug 30669. Basically it simplifies the use of linked resources and gives the user less opportunity to screw up. Oh yeah, sorry for the bad timing. I wasn't aware of the state of the Package Explorer linked resource support. I assume you don't use the CopyFilesAndFoldersOperation/MoveFilesAndFoldersOperation because you do a copy/move specific to JavaElements? If you used the UI operation you would behave consistent with the Navigator. feature removed Verified fixed in RC1 |