Issue 63 in gwt-tooling: Changing output folder does not remove old deployment path's from WST components file

[codesite...@google.com]

Comment #2 on issue 63 by dobesv: Changing output folder does not remove
old deployment path's from WST components file
http://code.google.com/p/gwt-tooling/issues/detail?id=63

Yes, it's gwt-tooling. Sadly WST doesn't seem to provide a way to mark
those paths
as belonging to gwt-tooling so it could be a bit tricky to correctly
determine which
paths to remove. It would be possible, but more work since it would have
to be
tracked separately.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings