Summary: | [breakpoints] When hitting breakpoint in jar dependency, things get a bit flaky | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Kris De Volder <kdevolder> | ||||
Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> | ||||
Status: | NEW --- | QA Contact: | |||||
Severity: | major | ||||||
Priority: | P3 | CC: | sarika.sinha | ||||
Version: | 4.17 | ||||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | Linux | ||||||
Whiteboard: | stalebug | ||||||
Attachments: |
|
Description
Kris De Volder
2020-11-02 18:40:17 EST
Reproducible with eclipse-jee-2020-09-R-linux-gtk-x86_64.tar.gz (In reply to Kris De Volder from comment #1) > Reproducible with eclipse-jee-2020-09-R-linux-gtk-x86_64.tar.gz can you provide a sample scenario for Eclipse Platform SDK ? > can you provide a sample scenario for Eclipse Platform SDK ?
Didn't I already? I described how to import a project put a breakpoint in a specific location and reproduce the problem.
If that's not a scenario, I'm not sure what is you want exactly.
(In reply to Kris De Volder from comment #3) > > can you provide a sample scenario for Eclipse Platform SDK ? > > Didn't I already? I described how to import a project put a breakpoint in a > specific location and reproduce the problem. > > If that's not a scenario, I'm not sure what is you want exactly. Not with eclipse-jee and spring framework. But if we can get a reproducible simple java project with jar dependency then it is easier for us to isolate the problem. > But if we can get a reproducible simple java project with jar dependency then it is easier for us to isolate the problem.
Okay I see what you mean. The thing is, I am not sure this problem is reproducible with simple java projects and setting up a project like that with source attachements etc is really quite involved. I don't really want to do this, because:
- it is quite a bit of work I think
- and I'm not even sure the bug will still be reproducible if we remove m2e from the mix. (It may or may not be part of the problem.)
I actually already put quite a bit of effort into filing this bug and documenting the reproduction steps in detail so someone else could follow them to the letter and get the same behavior. I was hoping that this would be sufficient for someone with knowledge of the Eclipse / JDT / M2E internals to debug it further.
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. |