Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please provide a "Ignore in this session" option if hot-code replace fails #347

Open
laeubi opened this issue Nov 12, 2023 · 1 comment · May be fixed by #558
Open

Please provide a "Ignore in this session" option if hot-code replace fails #347

laeubi opened this issue Nov 12, 2023 · 1 comment · May be fixed by #558

Comments

@laeubi
Copy link
Contributor

laeubi commented Nov 12, 2023

Currently when hot-code replace fails I get a dialog like this:

grafik

the only option seem to always ignore the problem, but it would be useful to only ignore it in this debug session.

@SarikaSinha
Copy link
Member

For most of the preferences, "Ignore for this session" might be valid.

SougandhS added a commit to SougandhS/eclipse.jdt.debug that referenced this issue Nov 11, 2024
Adds a checkbox to the HCR error alert box that allows users to ignore
HCR failures only for the current debug session, rather than applying it
to all future debug sessions.

Fixes : eclipse-jdt#347
@SougandhS SougandhS linked a pull request Nov 11, 2024 that will close this issue
3 tasks
SougandhS added a commit to SougandhS/eclipse.jdt.debug that referenced this issue Nov 11, 2024
Adds a checkbox to the HCR error alert box that allows users to ignore
HCR failures only for the current debug session, rather than applying it
to all future debug sessions.

Fixes : eclipse-jdt#347
SougandhS added a commit to SougandhS/eclipse.jdt.debug that referenced this issue Nov 11, 2024
Adds a checkbox to the HCR error alert box that allows users to ignore
HCR failures only for the current debug session, rather than applying it
to all future debug sessions.

Fixes : eclipse-jdt#347
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants