Xtext -> XPand Workflow - How to for new Eclipse version [message #721355] |
Thu, 01 September 2011 14:40 |
Johnnyboy Messages: 39 Registered: September 2011 |
Member |
|
|
Hi Supporters,
I want to prototypically realize a tool chain for MDSD for a software development division because of my master thesis. I read many books and other sources so far and know I decided to realize the following tool chain: Xtext for creating the grammar and for modelling the concret model (in the generated editor), after that code generation with XPand.
My Problem is that I only found old documentations like help.eclipse.org/helios/index.jsp which do not work for the newest version of eclipse (I have installed the SDK 3.70). At this side is descriped that I have to activate the checkbox for the option "Create a generator project" while creating a new Xtext project. But this check box isn't existing anymore and the generated file system is totally different from one descripted in the tutorial. At the actual Xtext-documentation from the official site there is only an example for Xtend descriped. But if I understood things right this is no language for M2T transformation.
Is there any good tutorial which works with the actual version of eclipse? Or is there any other way to help me? I searched for any other tutorial or anything else the whole day but I did not found anything which descriped how to realize such a workflow.
I would be pleased for any answer and thanks in advance
Jonnyboy
[Updated on: Thu, 01 September 2011 14:41] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
Re: Xtext -> XPand Workflow - How to for new Eclipse version [message #722096 is a reply to message #722093] |
Sun, 04 September 2011 12:21 |
|
Hi,
i guess you missed one keypoint in Xpand: Xpand Support different kinds of MetaMetamodels. You can even contribut your own if you like. One is Javabeans Metamodel which has imports "full::qualified::java::package::name". Another is the (dynamic) EMF Metamodel wich has imports "packagename". you can set the metamodel used in the differen workflow components in the workflow (default is JavaBeans) and in your generator projects Xpand/Xtend properties.
If you'd inially changed it to JavaBeans the long package name world work as well as the extensions that cound not be found.
~Christian
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de
Day Job: https://www.everest-systems.com
|
|
|
|
Re: Xtext -> XPand Workflow - How to for new Eclipse version [message #722102 is a reply to message #722100] |
Sun, 04 September 2011 12:44 |
|
Hi,
emfmetamodel => domainmodel
javabeansmetamodel => org::eclipse::xtext::example::domainmodel or what ever the fiull qualified package name is in your case
what about give autocomplete a chance and finding out that .eContainer works?
Please note that you will have to configure the use of EMFMetamodel in your workflow too. e.g
component = org.eclipse.xpand2.Generator {
metaModel = org.eclipse.xtend.typesystem.emf.EmfMetaModel {
metaModelPackage = "org.xtext.example.mydsl.myDsl.MyDslPackage"
}
...
}
But i reccoment to use javabeans metamodel since it is default.
~Christian
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de
Day Job: https://www.everest-systems.com
[Updated on: Sun, 04 September 2011 12:59] Report message to a moderator
|
|
|
|
|
|
|
|
|
Re: Xtext -> XPand Workflow - How to for new Eclipse version [message #722135 is a reply to message #722124] |
Sun, 04 September 2011 15:50 |
Johnnyboy Messages: 39 Registered: September 2011 |
Member |
|
|
Hi,
I had my xtext projects opened in the workbench and exported the plugin and imported the plugin after restarting. Unfortunatly I did not recognized that through the import my original project would be deleted -> but that is my fault...
Now many new errors occured:
register = org.eclipse.xtext.example.DomainmodelStandaloneSetup {} of course cannot work because the file was deleted. And in the xpand-file he also don't likes many things. At least syntax highlighting seems to be working now...
=> if I recreate my old deleted xtext project -> is there really a way to generate things and get highlighting without run as? Because if you import the exported plug-in you have to decide between the exported plugin and the original one (which have the same name) -> and you need the original project to do stuff like register = org.eclipse.xtext.example.DomainmodelStandaloneSetup {} I think but you also need the exported plugin so that the syntax highlighting works. Only to add the dependncies of th original projets didn't work (to activate syntax highlighting)
Tanks in advance
Jonnyboy
[Updated on: Sun, 04 September 2011 15:54] Report message to a moderator
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05329 seconds