Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 320642 - [EGL] Importing a non-existent file does not produce an error
Summary: [EGL] Importing a non-existent file does not produce an error
Status: CLOSED FIXED
Alias: None
Product: Epsilon
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Dimitris Kolovos CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-22 10:42 EDT by Louis Rose CLA
Modified: 2012-02-06 10:59 EST (History)
0 users

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 Louis Rose CLA 2010-07-22 10:42:56 EDT 
An EGL template that imports a non-existent file does not report any parse problems. In the development tools, no problem markers are shown.

The following template can be used to reproduce the problem:

[%import 'NonExistent.egl'; %]

The EGL editor reports no problems for the above template.
Comment 1 Louis Rose CLA 2010-07-22 10:45:16 EDT 
This is a regression, introduced by the recent EGL refactorings. EglPreprocessorModule returned a defensive copy of ParseProblems, meaning that all calls to getParseProblems().add() would not modify the underlying collection.

I've changed EglPreprocessorModule to return a reference to the underlying collection, which fixes this issue.
Comment 2 Louis Rose CLA 2010-07-22 10:47:55 EDT 
Fix and regression test checked into SVN. Assigning to Dimitris for build integration - thanks!
Comment 3 Dimitris Kolovos CLA 2010-09-06 09:30:37 EDT 
Fixed in the latest interim version.
Comment 4 Dimitris Kolovos CLA 2010-11-25 08:21:30 EST 
Fixed in 0.9.0.