Bug 533835 - "hot code replacement failed" - but shouldn't have been attempted.
Summary: "hot code replacement failed" - but shouldn't have been attempted.
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.7   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-04-19 14:22 EDT by Dave Dyer CLA
Modified: 2022-11-24 14:05 EST (History)
1 user (show)

See Also:

Attachments
replacement message (37.34 KB, image/jpeg)
2018-04-19 14:24 EDT, Dave Dyer 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 Dave Dyer CLA 2018-04-19 14:22:49 EDT 
I have multiple projects in the workspace, some of which have identically named classes, but share no sources.
When one of these projects has a running instance, and another unrelated project is built, I frequently see this
message (image attached).  The running instance has NO binary relationship to the one being built, so hot code
replacement shouldn't be attempted in the first place.     Note  - I suspect this is related to the problem of breakpoints
in one project affecting breaks in another if the class names are congruent.  Also, this is not a new problem.

-- Configuration Details --
Product: Eclipse 4.7.3.20180308-1800 (org.eclipse.epp.package.java.product)Installed Features:
 org.eclipse.platform 4.7.3.v20180301-0715
Comment 1 Dave Dyer CLA 2018-04-19 14:24:16 EDT 
Created attachment 273694 [details]
replacement message
Comment 2 Eclipse Genie CLA 2020-08-27 17:48:56 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 Dave Dyer CLA 2020-08-27 17:59:17 EDT 
this bug still exists and is the bane of my existance every day.
Comment 4 Eclipse Genie CLA 2022-11-24 13:47:26 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.
Comment 5 Dave Dyer CLA 2022-11-24 14:05:12 EST 
This bug still exists and bugs me every day.