ktmprabhu / spray

Automatically exported from code.google.com/p/spray
0 stars 0 forks source link

Initial creation of or change in of EMF domain model project not recognized in Spray project #231

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Create empty EMF project
2. Create ecore model file
3. Build up valid Ecore model
4. Create EMF Generator Model on top of ecore model file
5. Generate from EMF Generator Model
5. Create Spray project via wizard and select ecore package

What is the expected output? 
The import and the EClass reference on the diagram node are resolved.

What do you see instead?
 * at import
Multiple markers at this line - The import fmp.* cannot be resolved - The 
required feature 'modelType' of 
 'org.eclipselabs.spray.mm.spray.impl.DiagramImpl@4ab0342e{platform:/resource/
 org.eclipselabs.spray.featuremodeling.feature.diagram/model/diagram.spray#/0}' must be set
 * at diagram node: Couldn't resolve reference to EClass 'Project'.

Work around: Restart Eclipse

Related issue: Changing a once resolved domain model, e.g. change the name of 
an ECLass and regenerate - this change is not propagated to the Spray project, 
so in the Spray file the renamed EClass cannot be resolved - here also only 
restarting Eclipse helps.

Original issue reported on code.google.com by de.abg.r...@gmail.com on 23 Dec 2012 at 1:32

GoogleCodeExporter commented 8 years ago
What works is to import an existing domain model project and Spray project at 
once. Then the domain model is resolved immediately.

Original comment by de.abg.r...@gmail.com on 23 Dec 2012 at 1:46

GoogleCodeExporter commented 8 years ago
Changes not directly related to resources are discovered and handled properly 
now. 
A change is not immediately propagated to the spray model, only when you make 
the spray file dirty.

Original comment by de.abg.r...@gmail.com on 30 Dec 2012 at 10:08