Community
Participate
Working Groups
First time noticed on 3.6RC2 but reproduced on 3.6M1 as well. Steps to reproduce: 1. Share a Java project, modify a Java file but make sure the change causes a compilation error 2. Sync the project with repository (models on) 3. In the Sync view, turn on Change Sets model => You should be already able to notice that the change set (named <Unassigned> probably) does not show there is an error. If this is not true play around for a while with the modified file: solving the compilation error and then making it show up again. At the same time observe the sync view and the change set's decoration. Sometimes the error overlay sticks to the change sets, even though the compilation error is solved.
Created attachment 170156 [details] Snap #1 > You should be already able to notice that the change set does not show there is an error.
Created attachment 170157 [details] Snap #2 > Sometimes the error overlay sticks to the change sets, even though the compilation error is solved.
As a workaround you could re-sync (removing the current synchronization first) or simply switch to a different mode (eg from Outgoing Mode to Incoming Mode) and then switch back to the mode you started with.
For me, I was able to reproduce this pretty consistently yesterday. 1. Switch to change set mode. 2. Modify two files. 3. Put one file in a change set and leave one alone. 4. Create compiler errors in both files. 5. Fix the error in the file in a change set. 6. Now fix the error in the file that's in the unassigned change set. 7. The unassigned change set node should still have the error marker.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
