Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341198 - [MWE2] When running workflow for Xtext, wrong DSL is generated
Summary: [MWE2] When running workflow for Xtext, wrong DSL is generated
Status: CLOSED WONTFIX
Alias: None
Product: EMFT
Classification: Modeling
Component: MWE (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-29 05:11 EDT by Lothar Wendehals CLA
Modified: 2011-03-29 06:44 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lothar Wendehals CLA 2011-03-29 05:11:42 EDT 
Build Identifier: 1.0.2

We have multiple, depending DSLs with predefined Ecore models. When calling the MWE2 workflow to generate one language, the actual workflow that is called is the one of the depending sublanguage.
Example: DSL Pattern depends on DSL Types. Calling workflow for pattern generates DSL for Types.

Output for calling workflow GeneratePattern.mw2:
0    [main] INFO  lipse.emf.mwe.utils.StandaloneSetup  - Registering platform uri 'C:\Workspace'
2179 [main] INFO  ipse.emf.mwe.utils.DirectoryCleaner  - Cleaning C:\Workspace\de.xxx.dsl.pattern\..\de.xxx.dsl.types\src-gen
2182 [main] INFO  ipse.emf.mwe.utils.DirectoryCleaner  - Cleaning C:\Workspace\de.xxx.dsl.pattern\..\de.xxx.dsl.types.ui\src-gen
2320 [main] INFO  ipse.xtext.generator.LanguageConfig  - generating infrastructure for de.xxx.dsl.types.Types with fragments : ImplicitRuntimeFragment, ImplicitUiFragment, SubPackageAwareGrammarAccessFragment, JavaBasedContentAssistFragment
7828 [main] INFO  .emf.mwe2.runtime.workflow.Workflow  - Done.


Reproducible: Always
Comment 1 Sebastian Zarnekow CLA 2011-03-29 06:15:58 EDT 
Lothar, do both modules have the same name? Please make sure to use unique names for mwe2 modules.
Comment 2 Lothar Wendehals CLA 2011-03-29 06:44:52 EDT 
Thanks, Sebastian. This is actually the error. We copied the MW2 workflow and forgot the change the module name.