[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-bpmn2.dev] Working on the ecore merger tool

Hey guys,

the problem I'm seeing for example with Bug 357088 - XML
Serialization: incorrect order of children
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=357088) is, that the
ecore model has been modified manually. If we fix the bug by modifying
the merger tool and re-generating the ecore model, how can we be sure
that we don't forget to apply one of those manual changes?

So if we agree work on the merger, we have to identify those changes.
Then the merger has to be modified so that it can apply those changes
automatically. Otherwise every bug fix on the merger level would mean
to do a modification iteration on the ecore.

I'm getting the feeling, that this merger tool discussion is blocking
the hole development on the project. So a decision should be made
ASAP.

Regards,
Benedikt


Am 2. April 2012 17:31 schrieb Henning Heitkötter <hheitkoetter@xxxxxxxxxxxxxx>:
> Hi Benedikt, hi Reiner!
>
> Benedikt, sorry for the confusion, so let me explain:
> The initial version of the Ecore file of BPMN2 was created with the
> merger tool, because XSD and CMOF differ in quite a lot of aspects
> (e.g. naming and type of references). So, having both versions merged
> automatically was pretty much necessary.
> Changes that were necessary afterwards have exclusively been applied
> to the generated Ecore file. Hence, up to now, we have always pursued
> the second strategy mentioned by Benedikt.
>
> Based on this situation, I would propose to continue with this
> strategy. I think that all bugs mentioned could also be tackled that
> way. While I certainly see the benefits of the merger tool, I
> personally assume it to be too much work maintaining it to match the
> current state when the same can also be achieved on basis of the Ecore
> file.
> However, if you/we decide to go ahead with the merger tool anyway, I
> would certainly support and use the other strategy (apply changes to
> the merger instead of the Ecore file) afterwards, even though - as
> explained - I would not propose and promote this option myself due to
> the initial investment necessary.
>
> To sum it up, my proposal would be to continue with our current
> strategy, as long as no one steps up and adapts the merger tool to the
> current state.
>
> Regards,
> Henning
>
> PS: not to complicate things, but just to mention it - one can also
> use model transformation tools like QVTO to apply mass changes to the
> Ecore file. For example, I've used this approach to fix bug 373502.
>
> 2012/3/30 Hille-Doering, Reiner <reiner.hille-doering@xxxxxxx>:
>> Hi Benedikt, hi Henning,
>> all exchanged information is correct. However, I see a lot of value in Benedikt's idea to invest in the merge tool for the following reasons:
>> 1. There is not always a complete regeneration needed. E.g for the mentioned Bug my idea was to run the merger and let it just add a new custom attribute to the existing model. For those tasks it also helps to modularize the merger.
>> 2. For the more unlikely case that a full regernation is neede, e.g. for BPMN 2.1, a working strategy would be a regeration to a new model and then using EMF compare to manually merge in the new classes.
>>
>> Reiner.
>>
>> Am 30.03.2012 um 15:42 schrieb "Henning Heitkötter" <hheitkoetter@xxxxxxxxxxxxxx>:
>>
>>> So far, I (and we as a project) have neglected the maintenance of the
>>> merger tool in favor of changing the Ecore file directly, because the
>>> latter is easier to do and requires only one generation step, instead
>>> of two (Merger + Genmodel).
>>>
>>> What would be preferable with respect to new releases of the
>>> specification depends on the kind and amount of changes in these
>>> releases :-). However, if there were too many changes to apply them
>>> manually, we could still implement a new merge tool (based on the
>>> existing one), which could also incorporate our manual changes.
>>> So, in my opinion, we should dedicate our limited resources to other
>>> areas first.
>>>
>>> One thing to keep in mind if we decided to update the merger anyway /
>>> sometime: the genmodel file was also modified manually. Hence, we
>>> would have to check, which of these changes affected individual
>>> elements and how to align them with the merger.
>>>
>>> Regards,
>>> Henning
>>>
>>> 2012/3/30 Benedikt Ritter <beneritter@xxxxxxxxxxxxxx>:
>>>> Hey,
>>>>
>>>> the general question is, where are you going with the merger tool? Do
>>>> you want to use it for subsequent releases of the spec? Then the
>>>> project has to be in a maintainable state, with unit tests,
>>>> checkstyle, findbugs, etc.
>>>> Special configuration issues as mentioned by Henning should be
>>>> extracted from the code to some sort of config file (as far as
>>>> possible).
>>>>
>>>> If on the other hand, migrating the ecore by hand to a new spec
>>>> release is far less effort then re-generating it and adjusting the
>>>> generated model, it should be considered to drop the merge tool
>>>> completely.
>>>>
>>>> If you see a chance for bringing the tool up to date, then I'll start
>>>> right away, by writing some tests.
>>>>
>>>> Benedikt
>>>>
>>>>
>>>> Am 30. März 2012 14:28 schrieb Henning Heitkötter <hheitkoetter@xxxxxxxxxxxxxx>:
>>>>> Hi all,
>>>>>
>>>>> I recently had a look at the merger tool and generated a merged Ecore
>>>>> file for testing purposes. I found that our ecore file has diverged
>>>>> from the automatically generated file in a lot of areas. (Of course,
>>>>> you can also look at the git log for the file to see these changes.)
>>>>> I also had some problems with attribute types (the ecore file that I
>>>>> had generated from the CMOF file only used EJavaObject), but that
>>>>> might have been due to some configuration issues on my side.
>>>>>
>>>>> While I think that bringing the merger tool up-to-date with these
>>>>> changes might be useful for future changes to the specification, be
>>>>> advised that it will likely require a lot of work and manual
>>>>> modification of the generated file (or special rules) might still be
>>>>> necessary, as not all changes can be deducted from the specification
>>>>> (CMOF + XSD) alone.
>>>>>
>>>>> Regards,
>>>>> Henning
>>>>>
>>>>> 2012/3/29 Hille-Doering, Reiner <reiner.hille-doering@xxxxxxx>:
>>>>>> Hi Benedikt,
>>>>>> I'm fine with the idea. Feel free to reorganize the project to fit to Maven convention structure. Only note that for bundles (for which we use tycho), the structure is different and more PDE like - and bundle tests go to extra bundles or fragments.
>>>>>>
>>>>>> Regards,
>>>>>>  Reiner.
>>>>>>
>>>>>>
>>>>>> Am 29.03.2012 um 22:40 schrieb "Benedikt Ritter" <beneritter@xxxxxxxxxxxxxx>:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I'm planning to put some effort on the ecore merger tool, since there
>>>>>>> are several issues related with that tool (e.g.
>>>>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=357088 or the discussed
>>>>>>> splitting of the ecore model). However, I'm feeling uncomfortable,
>>>>>>> touching the code because there are no unit tests. So the first thing
>>>>>>> I want to do is to write some unit tests.
>>>>>>> Now at my company we use maven. Maven has a convention for the project
>>>>>>> structure, where unit tests reside in special source folder called
>>>>>>> src/test/java. Since the ecore merger tool does not stick to this
>>>>>>> convention, I do not know where to put my unit tests. I've seen the
>>>>>>> test bundle but I don't think that it is the right place for the ecore
>>>>>>> merger unit tests. So where should I put the tests?
>>>>>>>
>>>>>>> After bulding up a basic test coverage (and ATM I don't know how much
>>>>>>> effort that will be), I'd like to try to split the code up some more.
>>>>>>> The processor has several concerns that it has to deal with, and it
>>>>>>> would be good to separate concerns.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Benedikt
>>>>>>> _______________________________________________
>>>>>>> mdt-bpmn2.dev mailing list
>>>>>>> mdt-bpmn2.dev@xxxxxxxxxxx
>>>>>>> https://dev.eclipse.org/mailman/listinfo/mdt-bpmn2.dev
>>>>>> _______________________________________________
>>>>>> mdt-bpmn2.dev mailing list
>>>>>> mdt-bpmn2.dev@xxxxxxxxxxx
>>>>>> https://dev.eclipse.org/mailman/listinfo/mdt-bpmn2.dev
>>>>> _______________________________________________
>>>>> mdt-bpmn2.dev mailing list
>>>>> mdt-bpmn2.dev@xxxxxxxxxxx
>>>>> https://dev.eclipse.org/mailman/listinfo/mdt-bpmn2.dev
>>>> _______________________________________________
>>>> mdt-bpmn2.dev mailing list
>>>> mdt-bpmn2.dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/mdt-bpmn2.dev
>>> _______________________________________________
>>> mdt-bpmn2.dev mailing list
>>> mdt-bpmn2.dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/mdt-bpmn2.dev
>> _______________________________________________
>> mdt-bpmn2.dev mailing list
>> mdt-bpmn2.dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/mdt-bpmn2.dev
> _______________________________________________
> mdt-bpmn2.dev mailing list
> mdt-bpmn2.dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mdt-bpmn2.dev