Community
Participate
Working Groups
The purpose of this bug report is to highlight an area that is affected by concurrency. The current behavior is adequate but could possibly be improved. As the concurrency story is hammered out, we'll need to ensure that this operation continues to be well behaved. I performed the following scenario: 1) Loaded a plugin as a binary plugin (which create the appropriate Java index files). 2) Performed a background checkout on the project 3) As the checkout is proceeding, perform an open type on one of the types in the project. In 3.0 M3, the user is presented with a dialog indicating that the type could not be found. The failure was gracefull enough but it would have been nice if the user was presented with a message stating the reason. This may be made possible by improved delta support by Core (i.e. currenty a delta is only fired at the end of the operation but there is a plan to have deltas fire as the operation proceeds in order to provide the user with better feedback).
I am passining this one to JDT/Core since they create the delta. The all types cache currently listens to Java model deltas and updates its content accordingly. IMO this should work as soon as core resource fires deltas as the operation proceeds. JDT/Core listens to resource deltas and fires a corresponding Java model delta as soon as it receives a resource delta. But Core knows better ;-).
In I200212162000, I tried several 'Open type' operations while checking out a big projects. Each time the types presented in the Package Explorer were present in the dialog. This is expected as Java deltas are now fired when a resource delta comes in. Michael, can this be closed?
I was referring to the behavior when the types were selected and opened in the Open Types dialog. The error message I get seems reasonable so this can be closed.
Closing then.
