Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 324764

Summary: MoDisco Workflow : pb with Acceleo launching and "runner" parameter
Product: [Modeling] MoDisco Reporter: Fabien Giquel <fabien.giquel>
Component: InfrastructureAssignee: Gabriel BARBIER <barbier.gabriel>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: barbier.gabriel, hugo.bruneliere, modisco.web-inbox
Version: 0.9.0Flags: barbier.gabriel: indigo+
Target Milestone: 0.9.0 M2   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Fabien Giquel CLA 2010-09-08 11:52:36 EDT 
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.
Comment 1 Gabriel BARBIER CLA 2010-09-09 05:35:31 EDT 
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
Comment 2 Gabriel BARBIER CLA 2010-09-09 06:13:42 EDT 
After adding traces in the code, I reproduces the problem (because I used an Eclipse Application launched from my current Eclipse).
Comment 3 Gabriel BARBIER CLA 2010-09-10 09:06:26 EDT 
Fixed in revision 3014
Comment 4 Hugo Bruneliere CLA 2010-10-05 04:59:58 EDT 
Bug fixed.