Further integrate XText parser into Umple

[GoogleCodeExporter]

Scenario 1:

a)  Get a compilable version of the Xtext generated code. This code will live 
within cruise.umple under the /gen directory similar to our Jet templates. This 
will involve understanding the minimum about of generated code to "compile" 
Umple - the remainder of the generated code will reside in the UI / Ecore 
projects. This will require a list (and access to) several xtext jars.

b) Update UmpleXtextParser? to call the generated code and wrap their objects 
with Umple's. At this point we should be able to run the 
UmpleXtextParserTests?. 

c) Get all UmpleXtextParserTests? running, and do a spot check on the current 
tools (umple.jar and UmpleOnline? primarily) 

d)  Change the default parser from UmpleInternalParser? to UmpleXtextParser?. 
Look at compile the jar dependency files directly from source (or at least 
extracting them into our /bin) to ensure we can have a one jar compiler 

Scenario 2

make some form of translater to generate the Umple internal Grammar from the 
XText grammar or vice versa, so they are easily aligned.

Original issue reported on code.google.com by TimothyCLethbridge on 25 Jun 2011 at 2:07

[GoogleCodeExporter]

This was put on hold after extensive analysis. However here are the new 
requirements:

We want to automatically generate the XText grammar from the regular Umple 
grammar, so that the XText plugin for Eclipse can always be kept up to date. 
That may require some annotation of the regular grammar.

Original comment by TimothyCLethbridge on 15 Jun 2012 at 2:55

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by TimothyCLethbridge on 15 Jun 2012 at 2:55

• Added labels: Type-ProjectUG, Diffic-Med
• Removed labels: Type-Enhancement

[GoogleCodeExporter]

issue 319 and  issue 176  and issue 327 are all related

Original comment by TimothyCLethbridge on 13 Sep 2012 at 7:38

[GoogleCodeExporter]

Original comment by TimothyCLethbridge on 27 Sep 2012 at 8:11