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

Bug 318554

Summary: Errors while building the Workspace when Ecore.ecore is present in an Acceleo project
Product: [Modeling] Acceleo Reporter: Romain Guider <romain.guider>
Component: CoreAssignee: Project Inbox <acceleo-inbox>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: laurent.goubet
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
Message and stack trace none

Description Romain Guider CLA 2010-07-01 04:02:29 EDT 
Build Identifier: I20100527-1700

When Ecore.ecore is imported in an Acceleo project (so that we can generate code from Ecore models), the workspace build throws exceptions when it comes to building the acceleo project.

Reproducible: Always

Steps to Reproduce:
1. Create a sample acceleo project with the default template created by the wizard
2. Import Ecore.ecore somewhere in the project folder
3.
Comment 1 Romain Guider CLA 2010-07-01 04:03:49 EDT 
Created attachment 173170 [details]
Message and stack trace

This is the stack trace of the exception that is thrown while building the Acceleo project.
Comment 2 Laurent Goubet CLA 2010-07-06 04:35:00 EDT 
We introduced a facade for the package registry so that we wouldn't pollute the global package registry with workspace-defined packages anymore. It is now possible to work with Ecore.ecore or UML.uml in the workspace, remove classes or concepts from this metamodels and still be able to load ecore files properly.

In addition, Acceleo modules defined on a workspace metamodel will now react to changes done in these metamodels (concept added or removed ...).