Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362242 - Enumeration resolves differently for builder vs VE
Summary: Enumeration resolves differently for builder vs VE
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P1 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-27 16:35 EDT by Justin Spadea CLA
Modified: 2017-02-23 14:17 EST (History)
2 users (show)

See Also:

Attachments
Testcase (1.22 KB, application/octet-stream)
2011-10-27 16:36 EDT, Justin Spadea CLA 		no flags Details
View All 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 Justin Spadea CLA 2011-10-27 16:35:39 EDT 
Given the attachment, add a breakpoint to MVCTemplate.java line 974 "if (value instanceof EnumerationEntry) {"

When generating due to a compile (incremental build) the value is eglx.ui.SignKind, from the Java runtime. When generating for the VE it is an EnumerationEntry. It seems like they should resolve the same.
Comment 1 Justin Spadea CLA 2011-10-27 16:36:00 EDT 
Created attachment 206093 [details]
Testcase
Comment 2 Paul Harmon CLA 2011-11-07 13:47:11 EST 
I have update the MANIFEST.MF for org.eclipse.edt.mof to change the Eclipse-BuddyPolicy from "dependent" to "registered". This will keep the runtime projects our of the classpath when the XML files for our IRs are deserialzed.

I have also updated the manifest files for the following plugins to register their dependency:

org.eclipse.edt.mof.egl
org.eclipse.edt.mof.eglx.persistence.sql
org.eclipse.edt.mof.eglx.services
Comment 3 Justin Spadea CLA 2011-11-22 16:17:24 EST 
Verified