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

Bug 362242

Summary: Enumeration resolves differently for builder vs VE
Product: z_Archived Reporter: Justin Spadea <jspadea>
Component: EDTAssignee: Project Inbox <edt.compiler-inbox>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P1 CC: pharmon, svihovec
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
Testcase none

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