Re: [mdt-bpmn2.dev] Commit of Ecore Generation Tool

["Hille-Doering, Reiner" <reiner.hille-doering@xxxxxxx>]

Thanks Henning for the suggestions.

I followed them and committed both tools.

Soon I will also publish the articles that describe the tools and there result in detail.

 

Regards,

  Reiner.

 

PS: Feedback as usual welcome.

 

 

Von: mdt-bpmn2.dev-bounces@xxxxxxxxxxx [mailto:mdt-bpmn2.dev-bounces@xxxxxxxxxxx] Im Auftrag von Henning Heitkötter
Gesendet: Mittwoch, 29. September 2010 16:36
An: BPMN2 Developers Mailing List
Betreff: Re: [mdt-bpmn2.dev] Commit of Ecore Generation Tool

 

Hi Reiner,
excellent, I'm looking forward to these programs.

I'd opt for placing them under "org.eclipse.bpmn2.tools.*", for example org.eclipse.bpmn2.tools.merger or ...cmofAndXsd2Ecore, in order to separate these tools from our "product". I personally don't like omg2ecore as it's not quite descriptive.

For the XSLT program, perhaps org.eclipse.bpmn2.tools.xsltFromEcore?

In the long term we could also separate our projects into different folders inside the repository (like plugins, build, tests, examples, tools).

Please keep Eclipse's IP policy in mind when commiting, i.e. include only those parts that you wrote by yourself (e.g. nothing from the specification). Just a reminder, if that's what you would have done anyway, please ignore my comment :-).

Regards,
Henning

2010/9/29 Hille-Doering, Reiner <reiner.hille-doering@xxxxxxx>

Hi all,

I plan to commit the program that I used to merge the OMG CMOF and XSD that resulted in our first version of the .ecore model. I think this is useful for future releases of BPMN.

Does somebody has an idea how the project and thus the Java packages should be named?

E.g.

org.eclipse.bpmn2.ecoregenerator

org.eclipse.bpmn2.maintanance.omg2ecore

…

 

Thanks for any ideas,

Reiner.

 

PS: I also want to commit a second project that uses the merged ecore to derive the XSLTs that convert between XML and XMI. Name proposals for this second project are also welcome.