Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326331 - [tooling] Closing project does not invalidate meta-model
Summary: [tooling] Closing project does not invalidate meta-model
Status: CLOSED FIXED
Alias: None
Product: Acceleo
Classification: Modeling
Component: Core (show other bugs)
Version: 3.0.0   Edit
Hardware: PC Windows Vista
: P2 normal
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-27 13:59 EDT by Ed Willink CLA
Modified: 2015-05-27 08:56 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 Ed Willink CLA 2010-09-27 13:59:30 EDT 
3.0.1:

If a *.mtl file is being edited and using a *.ecore file in a workspace project, and then the project is closed, there are no resulting errors.

This is a demonstration of a more generic problem whereby the in memory ResourceSet retains stale declarations.
Comment 1 Stephane Begaudeau CLA 2011-09-02 03:56:46 EDT 
In Acceleo 3.1.1 (and I believe since 3.1.0), if a project containing an ecore file is closed, and if an Acceleo generator uses this ecore file as a metamodel then errors will appear when the mtl files will be edited. We could force a full build of all the acceleo projects that are depending on the now closed or deleted project.
Comment 2 Stephane Begaudeau CLA 2011-09-26 03:55:20 EDT 
Marking as resolve for 3.1.0 and 3.2.0
Comment 3 Laurent Goubet CLA 2015-05-27 08:56:55 EDT 
Closing resolved bugs