[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [buckminster-dev] How to improve mapping rules in the Aggregator
|
Thomas Hallgren wrote:
On 2009-12-08 10:45, Karel Brezina wrote:
Do we agree that version ranges are needed in the model? I think, it's
very annoying to update versions every time MDR is updated.
I agree. Version ranges are needed.
Great. We have a common thought :-)
Thomas, how would you add version ranges to the current model without
breaking it too much?
As a first step, I would replace the code that resolves the proxy
reference from the InstallableUnitReference to the InstallableUnit with
one that understands both the current URI and one using id + version range.
I can imagine this.
Second, I would make sure that when a reference is established (by user
selecting a mapped IU, either by drag-n-drop or by selecting in a list),
proxy URI using a range is created. Initially, this range would be open
ended.
When the reference to the IU is established, it refers to a resolved IU instance
and its proxy URI is undefined at that time.
The proxy URI is generated by the EMF resource implementation at the time
the model is being saved. It is unclear to me how we are going to hack this.
Even if we do, is that a proper usage of EMF?
Third, I would provide the GUI necessary to alter the range boundaries
(i.e. tweak the proxy). This is probably just a matter of adding a
custom derived property to the model (or perhaps more then one to bring
clarity).
This is also unclear to me - where do we add the properties? Are they
persistent/transient? How do we edit them?
Fourth, I would add the validation that verifies that selected features
don't overlap and doesn't create conflicts.
Sure, good thing. Although I think that feature overlap is not an error,
especially if the overlap comes from different contributions.
Filip
