Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 324764 - MoDisco Workflow : pb with Acceleo launching and "runner" parameter
Summary: MoDisco Workflow : pb with Acceleo launching and "runner" parameter
Status: CLOSED FIXED
Alias: None
Product: MoDisco
Classification: Modeling
Component: Infrastructure (show other bugs)
Version: 0.9.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 0.9.0 M2   Edit
Assignee: Gabriel BARBIER CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-08 11:52 EDT by Fabien Giquel CLA
Modified: 2010-10-18 08:39 EDT (History)
3 users (show)

See Also:
barbier.gabriel: indigo+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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.