Community
Participate
Working Groups
Having a separate, parallel mechanism to store the model's contents is, IMO, a bad thing. We should at least look into what happens if we just save / restore the model using EMF's standard patterns and then attempt to manage missing (or updated) bundles 'on the fly'. The best possible solution would also allow this to take place for Menu / TB contributions as well but if not we can still remove them on shutdown before saving the model. We will need some way (checksum??) to determine whether there have been any changes to the package structure since the last session ended. The 99% case is that we're starting up in the same state that we shut down in so we should optimize for this.
The 99% case is true for deployment but not for development time, where one adds/removes/moves stuff around
We also need to check that the final approach works OK for dynamic bundle addition/removal.
M2 is done...
Moving to M4; once we get trim dragging done it'll be more apparent why this makes sense...we may defer this to 4.3.
I'll move this to M7 (just so I can move it to 4.3 once the slot shows up), it's essentially off the plate for 4.2 since it's not causing issues....
The main issue is that we need to come up with some mechanism to prevent contributions from being added multiple times...
Already Done...
