Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 357768

Summary: [modeling] Interest is not propagated to parent resources (and Ecore file ends up with empty structure kind)
Product: z_Archived Reporter: Steffen Pingel <steffen.pingel>
Component: MylynAssignee: Miles Parker <milesparker>
Status: RESOLVED DUPLICATE QA Contact:
Severity: major    
Priority: P3 CC: shawn.minto
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on:    
Bug Blocks: 354787    
Attachments:
Description Flags
empty structure kind
none
interest not propagated to resource none

Description Steffen Pingel CLA 2011-09-15 06:31:08 EDT 
Steps:
1. Activate a new task
2. Unfocus Project Explorer
3. Select class element in Ecore model

I have observed that interest is sometimes not propagated to the resource and hence the context appears empty when filtered (see screenshot).

Possibly related, sometimes the resource is added with an empty structure kind.
Comment 1 Steffen Pingel CLA 2011-09-15 06:31:37 EDT 
Created attachment 203398 [details]
empty structure kind
Comment 2 Steffen Pingel CLA 2011-09-15 06:33:10 EDT 
Created attachment 203399 [details]
interest not propagated to resource
Comment 3 Miles Parker CLA 2011-09-15 15:07:49 EDT 
Yeah,, there is something really fishy going on there. I've gone back and forth on whether to include the actual ecore file location as a "resource" *content type* † and/or as an "ecore" content type. What I came down to is to include both the full URI i.e. "platform:/resource.." for 'ecore' and the file reference as the resource. I think we need both. In your case, both of those are badly wrong.

This is somewhat related to bug 357755 as well.

†this is potentially confusing because it is overloaded with EMF resource which means something very different, as it refers to a unique URI
Comment 4 Miles Parker CLA 2011-09-21 16:51:58 EDT 
There are two separate issues here. I haven't been able to reproduce the second one -- I think this might have been due to some funny stuff with packages. Let's open a new bug if that one comes up. I'm marking this as a dup of bug 357755 as the underlying issue is the same. See that bug for a followup.

*** This bug has been marked as a duplicate of bug 357755 ***