Community
Participate
Working Groups
fragment.merge() is always called (line 192) even when the element already exists and notexists tag is set.
Pushed a fix to https://git.eclipse.org/r/34817
Created attachment 251707 [details] Basic E4 application to show the not_exists merge problem The zip contains a simple e4 application project to reproduce this issue : - test-fragments is the main plugin containing the application model - fragment is a plugin that contributes a part to the main model using a fragment.xmi. This fragment is contributed using the "notexists" apply policy (see extensions tab of plugin.xml, fragment extension element details), meaning the fragment shall be merged only if not already found in the application model. Launch the app (clear workspace when prompted), select the "Fragment Part" view and click the button inside : this changes the label of the part to "Label 0", "Label 1", etc. Now quit the app and restart it without clearing the workspace. You'll notice that the contributed part is named "Fragment Part" again, meaning the fragment was merged again in the application model despite being tagged "notexists".
I forgot to mention that the example runs with Luna SR2 target platform
*** Bug 487748 has been marked as a duplicate of this bug. ***
*** Bug 547503 has been marked as a duplicate of this bug. ***
New Gerrit change created: https://git.eclipse.org/r/144622
This problem is hitting us really badly because parts get duplicated on restart after they were moved to a different part stack. I do not quite understand why the proposed fix is not getting accepted Jonas' comment does not make much sense to me either. Can we do anything to get it merged?
Mass move 4.19 M1 bugs to M3
Removing milestone from 4.19 M3 to 4.19, please re-target accordingly.
Mass move out of 4.19
Mass Move out of 4.20
