You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ae23fcb
Browse filesBrowse the repository at this point in the historyBrowse files
"Learn More" link jumps to the associated troubleshooting paragraph directly (microsoft#371)
* Learn More link to the corresponding troubleshooting paragraph directly
Signed-off-by: Jinbo Wang <jinbwan@microsoft.com>
* Update LS troubleshooting anchor point
* make tslint happy
* Give a meaningful sample message instead of xyz
* Refactor IMessage interface
Copy file name to clipboardExpand all lines: Troubleshooting.md
+16-3Lines changed: 16 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,11 @@ The debugger works with [Language Support for Java(TM) by Red Hat](https://marke
18
18
19
19
## Failed to resolve classpath:
20
20
### Reason:
21
+
Below are the common failure reasons.
22
+
- Main class 'C:\demo\org\microsoft\app\Main.java' doesn't exist in the workspace.
23
+
- Main class 'org.microsoft.app.Main' isn't unique in the workspace.
24
+
- The project 'demo' is not a valid java project.
25
+
21
26
In launch mode, the debugger resolves the classpaths automatically based on the given `mainClass` and `projectName`. It looks for the class specified by `mainClass` as the entry point for launching an application. If there are multiple classes with the same name in the current workspace, the debugger uses the one inside the project specified by `projectName`.
22
27
23
28
### Try:
@@ -65,7 +70,7 @@ You configure the incorrect main class name in `mainClass` of *launch.json*.
65
70
66
71
### Try:
67
72
1. Check whether the class name specified in `mainClass` exists and is in the right form.
68
-
2. If the problem persists, it's probably because the language server doesn't load your project correctly. Please reference *"Java Language Support extension fails to start"* paragraph for more troubleshooting info.
73
+
2. If the problem persists, it's probably because the language server doesn't load your project correctly. Please reference the [language server troubleshooting](#try) paragraph for more troubleshooting info.
69
74
70
75
## The DEBUG CONSOLE throws ClassNotFoundException
71
76
### Reason:
@@ -74,12 +79,20 @@ This error indicates your application attempts to reference some classes which a
74
79
### Try:
75
80
1. Check whether you configure the required libraries in the dependency settings file (e.g. *pom.xml*).
76
81
2. Run VS Code command *"Java: Force Java compilation"* to force the language server to rebuild the current project.
77
-
3. If the problem persists, it's probably because the language server doesn't load your project correctly. Please reference *"Java Language Support extension fails to start"* paragraph for more troubleshooting info.
82
+
3. If the problem persists, it's probably because the language server doesn't load your project correctly. Please reference the [language server troubleshooting](#try) paragraph for more troubleshooting info.
78
83
79
84
## Cannot find a class with the main method
80
85
### Reason:
81
86
When the `mainClass` is unconfigured in the *launch.json*, the debugger will resolve a class with main method automatically. This error indicates the debugger doesn't find any main class in the whole workspace.
82
87
83
88
### Try:
84
89
1. Check at least one main class exists in your workspace.
85
-
2. If no main class exists, please create a main class first. Otherwise, it's probably because the language server fails to start. Please reference *"Java Language Support extension fails to start"* paragraph for more troubleshooting info.
90
+
2. If no main class exists, please create a main class first. Otherwise, it's probably because the language server fails to start. Please reference the [language server troubleshooting](#try) paragraph for more troubleshooting info.
91
+
92
+
## Build failed, do you want to continue?
93
+
### Reason:
94
+
The error indicates your workspace has build errors. There are two kinds of build errors. One is compilation error for source code, the other is project error.
95
+
96
+
### Try:
97
+
1. Open VS Code PROBLEMS View, and fix the errors there.
98
+
2. If no errors are found in the PROBLEMS View, reference the [language server troubleshooting](#try) paragraph to update project configuration, and clean workspace cache.
0 commit comments