Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326260 - References to imported metamodel cannot resolved
Summary: References to imported metamodel cannot resolved
Status: CLOSED FIXED
Alias: None
Product: Acceleo
Classification: Modeling
Component: Core (show other bugs)
Version: 3.0.0   Edit
Hardware: PC Windows 7
: P3 normal
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-26 15:06 EDT by Mirko Seifert CLA
Modified: 2011-04-29 10:26 EDT (History)
1 user (show)

See Also:

Attachments
Example project that reproduces the bug (9.93 KB, application/zip)
2010-09-26 15:12 EDT, Mirko Seifert CLA 		no flags Details
View All 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 Mirko Seifert CLA 2010-09-26 15:06:19 EDT 
When creating a template the uses metamodels from the workspace, references between metamodels cannot resolved. I'll attach a minimal test case which reproduced the bug.

The test plug-in contains two metamodels (imported_mm.ecore and importing_mm.ecore). When I use a metaclass from importing_mm.ecore (i.e., class 'Subclass') the features of class 'Superclass', which is from imported_mm.ecore cannot be resolved.

To explore the bug just import the attach plug-in archive and open the 'generate.mtl' file.

Let me know if you need further information.
Comment 1 Mirko Seifert CLA 2010-09-26 15:12:42 EDT 
Created attachment 179591 [details]
Example project that reproduces the bug
Comment 2 Stephane Begaudeau CLA 2011-04-29 10:03:59 EDT 
The fix has been contributed on HEAD. It will be available in Acceleo 3.1.0 M7.
Comment 3 Mirko Seifert CLA 2011-04-29 10:26:08 EDT 
Great! I've tried this a few days ago with 3.7M6 where it did not work and with the sources from the CVS where it worked as expected. I was a little confused because the bug seemed to be fixed, but the bug was not yet tagged as being fixed. I was waiting for 3.7M7 to check again :)

Anyway, thanks for fixing!