-
Notifications
You must be signed in to change notification settings - Fork 373
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
Some log info should be debug traces #2603
Milestone
Comments
mickaelistria
added a commit
to mickaelistria/eclipse.jdt.ls
that referenced
this issue
Apr 18, 2023
mickaelistria
added a commit
to mickaelistria/eclipse.jdt.ls
that referenced
this issue
Apr 18, 2023
mickaelistria
added a commit
to mickaelistria/eclipse.jdt.ls
that referenced
this issue
Apr 18, 2023
mickaelistria
added a commit
to mickaelistria/eclipse.jdt.ls
that referenced
this issue
Apr 24, 2023
mickaelistria
added a commit
to mickaelistria/eclipse.jdt.ls
that referenced
this issue
Apr 24, 2023
rgrunber
pushed a commit
that referenced
this issue
Apr 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
JDTLanguageServer has a lot of
logInfo(...)
for most operations. Those will fill the Eclipse log file, and if integrated in Eclipse IDE, this will fill the logConsole with information that is usually not useful.This kind of logging looks more like debug traces, it would be better to guard it with some condition. Eclipse Platform offers
Platform.getDebugOption("<plugin>/<flag>")
that can be used to configure debug trace enablement.The text was updated successfully, but these errors were encountered: