Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318554 - Errors while building the Workspace when Ecore.ecore is present in an Acceleo project
Summary: Errors while building the Workspace when Ecore.ecore is present in an Acceleo...
Status: CLOSED FIXED
Alias: None
Product: Acceleo
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-01 04:02 EDT by Romain Guider CLA
Modified: 2010-07-06 04:35 EDT (History)
1 user (show)

See Also:

Attachments
Message and stack trace (5.11 KB, text/plain)
2010-07-01 04:03 EDT, Romain Guider 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 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 ...).