Bug 566263 - Cannot use Detailed Formatter with EMF application model elements
Summary: Cannot use Detailed Formatter with EMF application model elements
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.16   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-21 07:47 EDT by Lars Vogel CLA
Modified: 2022-09-29 10:18 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Vogel CLA 2020-08-21 07:47:38 EDT
MPart has a method getParent(), if I try to set this in the Debugger as detailed formatter I get the following exception:


Detail formatter error:
		The type org.eclipse.emf.common.notify.NotificationChain cannot be resolved. It is indirectly referenced from required .class files
		The type org.eclipse.emf.common.util.EList cannot be resolved. It is indirectly referenced from required .class files
		The type org.eclipse.emf.common.util.EMap cannot be resolved. It is indirectly referenced from required .class files
		The type org.eclipse.emf.ecore.EClass cannot be resolved. It is indirectly referenced from required .class files
		The type org.eclipse.emf.ecore.EStructuralFeature cannot be resolved. It is indirectly referenced from required .class files
		The type org.eclipse.emf.ecore.InternalEObject cannot be resolved. It is indirectly referenced from required .class files


To replicate: Start runtime Eclipse put a breakpoint at MPart.getParent() and try to use a Detailed Formatter in the Variables view for the caller of the method.
Comment 1 Eclipse Genie CLA 2022-09-29 10:18:09 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.