Community
Participate
Working Groups
Build 20020518 Scenario: - create a WEB project (WSAD M5 driver) - select the folder Web Content - rename that folder to Web Content2 observe: during the rename WASD somehow recreates the old Web Content folder. As a result undoing the rename ends in an error dialog saying that the resource already exists. There are several options to fix this: - the undo manager also listens to resource deltas (currently only listens to Java Model deltas) to flush the undo stack in this case. - we don't provide undo for renaming non Java resources. In this case we would use the Workbench actions instead of the Java actions. Doesn't block us to start first test fix pass. But should be addressed in first fix pass.
Listening to resource deltas doesn't fix the problem since refactoring unregisters the listener during change execution. The problem is that WSAD changes the element tree in PRE or POST auto build and refactoring has no change to figure this out. Talking to Core how to solve the problem
Lowering priority since this will not be addressed in F3
There is now way how refactoring can detect this case and do the right thing. The refactoring still flags the undo as not processable which results in the fact that the refactoring can't be undo in this case. Instead of recreating the element WSAD should now use the new refactoring participant architecture.
