Task: Generate org.xspray.mm classes in the build process

[GoogleCodeExporter]

The metamodel classes in org.xspray.mm can be generated any time from the 
genmodel, and this can be automated in the build.

TODO:
- check metamodel classes for manual code. There is a derived attribute "path" 
for migration purposes of the templates that was introduced in issue#6
- Put the code into extension classes
- add MWE workflow to the project
- execute workflow in the build
- remove classes from src

Original issue reported on code.google.com by karsten....@googlemail.com on 9 Sep 2011 at 11:10

[GoogleCodeExporter]

Original comment by karsten....@googlemail.com on 11 Sep 2011 at 11:17

• Added labels: Type-Task

[GoogleCodeExporter]

EMF Classes will be generated to `org.xspray.mm/emf-gen`.

A workflow `GenerateXsprayMM.mwe2` has been added to the project. This workflow 
is executed during the Maven build.

Manual implemented methods in the impl. classes (MetaAttribute#getPath()) have 
been replaced by extension methods in XsprayExtensions. Some minor 
modifications to the template were required.

Solved from build#30 on
https://spray.ci.cloudbees.com/job/spray-ci-build

Original comment by karsten....@googlemail.com on 11 Sep 2011 at 11:31

• Changed state: Fixed