-
Notifications
You must be signed in to change notification settings - Fork 31
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
More logging #300
Comments
See https:/eclipse/lemminx/blob/b11ed6b6fa20e141ef7bbe28b883b5b51986be13/org.eclipse.lemminx/src/main/java/org/eclipse/lemminx/logs/LogHelper.java#L38 . Currently this is set to log to a file using the Java logging API. On
|
See eclipse-wildwebdeveloper/wildwebdeveloper#974 (comment) for an example of how LemMinX logging can be harder than it seems. |
Any contribution are welcome for LemMinx to fix this issue. |
We've used the current log strategy and settings in Wild Web Developer, and they're good enough at the moment. No need for extra work here. |
We should provide a way to enable more logging in LemMinX-Maven, as many issues found in m2e are hard to debug. Logging should be off by default but easy enough to turn on with some system property for instance. Log should be written to file to not pollute the standard streams that LSP connection may use.
@angelozerr Does lemminx provide some logging strategy to reuse? Or a logging technology to use? Ideally, I'd like to go for
System.Logger
.The text was updated successfully, but these errors were encountered: