Community
Participate
Working Groups
Given an Acceleo launcher whith specific choice "Java application" for the runner rather than "Acceleo plugin application". Creating and launching a MoDisco workflow launcher with a call to the acceleo launcher -> the Acceleo launcher is always executed with the "Acceleo plugin application" runner and not the chosen runner.
Hello Fabien, I was not able to reproduce the problem. Here is the scenario I've used: Using the code generation in plug-in oegm.java.generation, I have create a launch configuration of type Acceleo. Then I have tested it with runner's parameter as "Acceleo plugin application", it fails with lots of error (a bug in acceleo registry). Then I switched the runner's parameter to "Java Application", and it runs correctly. So I switched back to "Acceleo plugin application" and created a launch configuration of type Modisco Workflow. I had the same behaviour as executing the launch configuration of type Acceleo standalone. I switched again the runner's parameter to "Java Application", and executed successfully the launch configuration of type Modisco Workflow. So if you have a different use case, let me know. Gabriel
After adding traces in the code, I reproduces the problem (because I used an Eclipse Application launched from my current Eclipse).
Fixed in revision 3014
Bug fixed.