Community
Participate
Working Groups
build I20031111 - loaded some changes from HEAD - incremental build - some of the problems in the Problems view are missing their attributes (see attached screen shot) I don't believe that the Problems and Tasks views properly handle the case where a marker's attributes are set in a separate operation from the marker creation. However, previously this never happened because the builder ran as a single operation (Tasks are created in a single workspace operation). Due to concurrent builds, is it now possible for this to happen, or should this be viewed as a regression? What is the granularity of locking for the Java builder, and how frequently are deltas sent?
Created attachment 6768 [details] Screen shot
To answer your questions, the workspace is locked at the root level for the duration of the build, but we don't supress periodic notifications. However, from looking at the marker view code it looks like it handles attribute change notification just fine. I.e., even if the creation and attribute change happened in separate deltas it should still work.
Moving back to UI then for now.
*** This bug has been marked as a duplicate of 83992 ***