Bug 536810 - Breakpoint does'nt show .class but .java on Maven module.
Summary: Breakpoint does'nt show .class but .java on Maven module.
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.8   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: 2018-07-08 21:33 EDT by yuki hane CLA
Modified: 2022-11-18 16:03 EST (History)
3 users (show)

See Also:

Attachments
window capture (96.62 KB, image/png)
2018-07-08 21:33 EDT, yuki hane 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 yuki hane CLA 2018-07-08 21:33:30 EDT 
Created attachment 274879 [details]
window capture

When setting breakpoint at maven module source file and debugging, stopped at .java file on Eclipse Photon.

on Eclipse Oxygen, stopped at .class file.

So, Photon does not work Expressions view.
Comment 1 Eclipse Genie CLA 2020-10-17 09:37: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.
Comment 2 Sarika Sinha CLA 2020-10-19 07:04:59 EDT 
@Gayan,
Do you see this happening now also?
Comment 3 Gayan Perera CLA 2020-10-19 08:21:26 EDT 
@Sarika i can check
Comment 4 Eclipse Genie CLA 2022-11-18 16:03:25 EST 
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.