|
Re: [Acceleo] Problem getting Run as | Launch Acceleo [message #636044 is a reply to message #635879] |
Fri, 29 October 2010 07:03 |
|
Hi,
We tested Acceleo on Helios and I have never seen this problem. I have two theory for this one, a new bug or a mistake that can easily be made. Let's start by being pessimistic:
Does the same thing occurs if your create your run configuration from scratch ?
Menu "Run" (not Run As on your project but Run at the top of the Eclipse window) then "Run Configurations...", then right click on "Acceleo Application" and "New", and then you have to select:
1- The acceleo project
2- The java class generated by Acceleo. This Java class has been created by Acceleo because in one template of one of your modules you have a [comment @main/]. This Java class is located in the same package as your module with your main template and it should have the same name as your module.
3- your model
4- your target folder
And then you can just click run. The generation should work. If it does, then I have an idea on what append previously, but if it doesn't could you please upload a picture of your Run Configuration.
If it worked, then I think that when you selected Run As on your project, Acceleo tried to look for the Java class that launch the generation and for that a window appears with the available Java files. You may have selected another Java class and not the Java class of your main module. In such case Acceleo cannot launch the generation.
Anyway, we you hit Run, the Acceleo engine is initialized and the generation starts it should not take more than few seconds. For example, I took 10s to initialize the generation and 9s to generate 200k lines of code today for me, so no need to wait for 10min.
Stephane Begaudeau, Obeo.
|
|
|
|
|
|
|
Re: [Acceleo] Problem getting Run as | Launch Acceleo [message #636633 is a reply to message #636469] |
Tue, 02 November 2010 09:56 |
|
Hi Daniel,
Your generation modules (mtl files) are taking their types from the Ecore metamodel (the "http://........../2002/Ecore" part of your modules' signatures), yet you feed them an "UML" model for the generation.
Your template would generate a file for an "EClass" in the source model, yet your UML model can't have any EClass : it will have "Class"es instead.
You can either change your sample module to take its type from the UML metamodel instead of Ecore, or change the sample model you feed the generation to be an ecore model instead of an UML model.
Laurent Goubet
Obeo
|
|
|
|
Powered by
FUDForum. Page generated in 0.04485 seconds