Community
Participate
Working Groups
Changing the file name of a test asset in the Test Navigator updates the logical name. [See https://bugs.eclipse.org/bugs/show_bug.cgi?id=162407#c17]: Jerome, if the user is renaming the physical name of a test asset, we should not rename the logical name, since they are separate names. Maybe we could ask the user if they would like the rename the logical name at the same time, but we should not assume they want them to be the same. The solution is to add a line in "refactoring" page of rename wizard saying "updating logical name" and checked by default.
Jerome, please provide a sizing.
tryed the proposed solution (adding a line inside refactoring page to separate logical renaming from physical renaming) it works well for pure renaming but there is a problem concerning the updating of linked ressource updating mecanism for linked ressource update at same time the logical and the physical name so, separating them would need to split this public API to have 4 update method instead of 2 : . update self when logical name change . update self when physical name change (instead of "update self when logical and physical name change") . update resource when linked logical name change . update resource when linked physical name change (instead of "update resource when linked logical and physical name change") also, there is a need to link the choice of the user inside refactoring wizard : if user unselect "change logical name", it should automatically unselect "update logical name" if user unselect "change physical name", it should automatically unselect "update physical name" so, it's less trivial that it seems. estimated time to do it : around 1 to 2 week + API change
(In reply to comment #2) > tryed the proposed solution (adding a line inside refactoring page to separate > logical renaming from physical renaming) > it works well for pure renaming but there is a problem concerning the updating > of linked ressource > updating mecanism for linked ressource update at same time the logical and the > physical name > so, separating them would need to split this public API to have 4 update method > instead of 2 : > . update self when logical name change > . update self when physical name change > (instead of "update self when logical and physical name change") > > . update resource when linked logical name change > . update resource when linked physical name change > (instead of "update resource when linked logical and physical name change") > > also, there is a need to link the choice of the user inside refactoring wizard > : > if user unselect "change logical name", it should automatically unselect > "update logical name" > if user unselect "change physical name", it should automatically unselect > "update physical name" > > so, it's less trivial that it seems. > estimated time to do it : > around 1 to 2 week + API change > Jerome, please update the Orig. Est. field with your estimate.
update estimated hours
Deferring to future as approved by the TPTP PMC (http://dev.eclipse.org/mhonarc/lists/tptp-pmc/msg04926.html).
Deferring to 4.5.2 given the lack of resources to complete in 4.5.1.
Deferring to TPTP 4.5.3 since TPTP 4.5.2 development is closed (http://www.eclipse.org/tptp/home/project_info/releaseinfo/4.5.2/schedule.html) and P2 defects are not considered candidates during release shut-down.
This scenario will be covered under 290254. *** This bug has been marked as a duplicate of bug 290254 ***
