MDS/openide
1
0
Fork 0
mirror of https://gitflic.ru/project/openide/openide.git synced 2025-12-16 22:51:17 +07:00
Code Issues Packages Projects Releases Wiki Activity

Feature Trainer. Proofread the 'Debug workflow' lesson

Browse Source 
GitOrigin-RevId: 822efa404a1b9c2f914ee7ecbbe3786c4bcdedcf
This commit is contained in:
Dmitry Matveev
2023-03-06 14:00:31 +01:00
committed by intellij-monorepo-bot
parent 03b371c801
commit b774540464
2 changed files with 30 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
java/java-features-trainer/resources/messages/JavaLessonsBundle.properties
View File

@@ -157,10 +157,11 @@ java.find.help.link=Search for a target within a file
java.debug.workflow.hotswap.disabled.warning=The <strong>Hot Swap</strong> feature is disabled in the IDE settings. \
Enable it in {0} | {1} | {2} <strong>\u2192</strong> {3} or just <callback id="{4}">click to activate</callback>.
java.debug.workflow.rebuild=For big programs, rerunning can take a long time. If you find and fix a mistake in a pure method, you can just rebuild \
the project and apply the <strong>Hot Swap</strong> JVM feature. Let''s build the project: {0}.
java.debug.workflow.confirm.hot.swap=Confirm the <strong>Hot Swap</strong> replacement.
java.debug.workflow.rebuild=We could rerun our small program after the fix, but for big programs, rerunning can take a long time. \
If the fix only affects a pure method (as in this case), we can rebuild the project and apply <strong>Hot Swap</strong> instead of rerunning. \
Press {0} to build the project.
java.debug.workflow.confirm.hot.swap=Confirm the <strong>Hot Swap</strong> reload.
java.debug.workflow.no.confirmation=<strong>Hot Swap</strong> is done automatically in the background. You may see a corresponding message in the lower-left corner.
java.debug.workflow.drop.frame=We patched our method, but right now we are still executing obsolete {0}, and it will throw the \
exception again. Let''s drop the frame and return to the state before the {1} call. Click {2} near the top method in the stack frame or press {3}.
java.debug.workflow.drop.frame=We''ve patched our method, but we are still executing the obsolete {0}, which will throw the \
exception again. Let''s drop the frame and return to the state before {1} was called. Click {2} near the top call in the stack frame or press {3}.
java.debug.workflow.invalid.drop=It seems that you performed an action that was not planned by the lesson. Please, restart the lesson.