Bug 242404

Description Kyle Krull 2008-07-29 11:30:53 EDT

The problems view does not seem to re-populate the issues it displays when it is configured to show errors and warnings for the window working set.

Specifically, the problems view does not update when moving projects (via Package Explorer) from the "Other Projects" working set to the set that has been selected as the window working set.  The issues associated with the re-assigned project do not show up until re-selecting the window working set under Problems->Configure Contents:

Steps to reproduce:
1. Make a working set with a project in it that has some issues, and select that as the window working set (Window->Working Sets->(whatever set you just made)
2. Problems->Configure Contents:
2a. Create a new configuration "Window working set"
2b. Select "match any configuration"
2c. Select errors and warnings of all types
2d. Set scope to "On working set"
2e. Click "select", and choose "window working set" in the new dialog
3. Package Explorer: Drag a project from another working set into the window working set.  At this point, the problems view still shows the original issues.
4. Problems->Configure Contents:
4a. Press "Select" again and press "ok" on the dialog where "window working set" is still selected
4b. Press ok on the "configure contents" dialog
4c. The problems view now updates with the new issues

Possible solutions:
1. Make the problems view update each time the selected working sets are updated, similarly to the Synchronize view.  Given the similarity that both views can show contents related to the window working sets, I'd expect to see similar behavior in terms of how they update their contents (i.e. they should both auto-refresh)
2. Add a refresh button / key to the problems view to "check it again", even if internally it thinks that it's already up to date.  Again, this would be similar to the Synchronize view

Platform:
Eclipse Build ID: I20080617-2000
Mac OS X: Version 10.4.11