Bug 534911 - When i debug or run junit method for class than throws internal exception
Summary: When i debug or run junit method for class than throws internal exception
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.7.2   Edit
Hardware: PC Windows 10
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-21 06:58 EDT by Sagar Makwana CLA
Modified: 2022-08-09 02:37 EDT (History)
1 user (show)

See Also:

Attachments
Exception screenshot for this issue (236.71 KB, image/png)
2018-05-21 06:58 EDT, Sagar Makwana 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 Sagar Makwana CLA 2018-05-21 06:58:56 EDT 
Created attachment 274115 [details]
Exception screenshot for this issue

I am working on Spring and also writing Junit for my classes and my class also contains auto wired object

every time when i run or debug junit than it will show me one modal like internalexception.

i have also attached screenshot with this bug.

Thanks
Comment 1 Sarika Sinha CLA 2018-05-22 00:16:54 EDT 
Please provide a sample project to be reproduce the problem for plain eclipse SDK.
Comment 2 Eclipse Genie CLA 2020-08-15 15:00:42 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.
Comment 3 Eclipse Genie CLA 2022-08-09 02:37:52 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.