Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362158 - Metamodel may not be omitted from the module declaration
Summary: Metamodel may not be omitted from the module declaration
Status: CLOSED WONTFIX
Alias: None
Product: Acceleo
Classification: Modeling
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows Vista
: P3 minor
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-27 04:02 EDT by Ed Willink CLA
Modified: 2016-04-06 10:39 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2011-10-27 04:02:02 EDT
It is possible to write an imported module that provides helper queries and templates using only the Standard Library types, so no metamodel is necessary for resolving declarations.

If the meta-model is omitted on te module declaration (wirth or without empty parentheses) a "The metamodel is required" is produced.
Comment 1 Laurent Goubet CLA 2011-10-27 04:38:39 EDT
That was once working, and should anew. This will be in 3.3 (3.2 will be release next week and we no longer change it).
Comment 2 Laurent Goubet CLA 2016-04-06 10:39:46 EDT
This actually never worked (checking the history) and would require changes throughout the parser since it assumes it has a metamodel in many places. This is a minor annoyance for people creating "utility" templates without any use of modelled types, so we do not plan on changing this behavior.