Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 356570 - need ability of eTrice generator model to handle the case of libraries
Summary: need ability of eTrice generator model to handle the case of libraries
Status: CLOSED FIXED
Alias: None
Product: eTrice
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: 0.1.0
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-02 07:02 EDT by Henrik Rentz-Reichert CLA
Modified: 2011-12-16 02:48 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 Henrik Rentz-Reichert CLA 2011-09-02 07:02:58 EDT 
To support model libraries the generator model should add all ROOM classes to the respective lists of used classes.
The library case is defined by no SubSystemClass available in the models on the main path (the path where the first model resides)
Comment 1 Henrik Rentz-Reichert CLA 2011-09-02 08:40:04 EDT 
done with
e945190e5e65b1f9da20e903de90ba61ec872e70
Comment 2 Henrik Rentz-Reichert CLA 2011-09-02 09:07:54 EDT 
If the creation of the generator model is driven by a modeling workflow (mwe) then it must be dealt with the fact that the standard Reader collects all models found on the classpath.
A typical situation is that the eTrice modellib with its timing and socket services including SubSystemClasses for test purposes is also passed in the list of models.

Therefore the first model is assumed as main model and only those models that reside in the same path are searched for SubSystemClasses.
If the main model has no eResource (would be the case for an in-memory model) then all models with no eResource are considered.

For convenience the Root class has a new method isLibrary() which can be used by the code generator.
Comment 3 Henrik Rentz-Reichert CLA 2011-09-02 12:05:38 EDT 
It makes sense that in the non-library case also only SubSystemClasses found on the main model path are considered.

This is implemented with
f1d10eb7125e89ba2e0de209c8fd17b4ce8ec72a
Comment 4 Henrik Rentz-Reichert CLA 2011-12-16 02:45:37 EST 
closed resolved bug
Comment 5 Henrik Rentz-Reichert CLA 2011-12-16 02:48:12 EST 
tagged as version 0.1.0