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

m2e logs #2367

Closed
karlvr opened this issue Mar 21, 2022 · 4 comments · Fixed by #2375
Closed

m2e logs #2367

karlvr opened this issue Mar 21, 2022 · 4 comments · Fixed by #2375

Comments

@karlvr
Copy link
Contributor

karlvr commented Mar 21, 2022

I have a Maven build process getting into an infinite loop state, where it's constantly building (I can see it repeatedly spawning processes that should be started once during the build). I would like to see the m2e log, like I did in Eclipse, to try to get a handle on what's going on, but I don't seem to be able to see any output from m2e. Am I missing something or is this something that we could add?

@rgrunber
Copy link
Member

rgrunber commented Mar 21, 2022

Regarding your main issue, it seems similar to #2360 .

For the logging question, have a look at eclipse-jdtls/eclipse.jdt.ls#1589 (comment) . Come to think of it we should probably add this to the Wiki if it isn't already.

Basically, adding jdt.ls.debug=true as a property to the java.jdt.ls.vmargs should enable DEBUG level logging at ${workspace}/.metadata/.out-jdt.ls-${timestamp}.log

eg. "java.jdt.ls.vmargs": "-XX:+UseParallelGC -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -Dsun.zip.disableMemoryMapping=true -Xmx1G -Xms100m -Djdt.ls.debug=true"

For reference, the default configuration is https://github.com/eclipse/eclipse.jdt.ls/blob/master/org.eclipse.jdt.ls.core/logback.xml . There is the ability to provide a custom configuration as well, but I think just setting the property should do what you need.

@rgrunber rgrunber added the bug label Mar 21, 2022
@rgrunber
Copy link
Member

Closing this out for now as the main issue should be fixed in our next release. There's also #2360 (comment) where we publish snapshot builds, and in the future we'll be publishing "insider" builds making it easier for consumers to try builds under development.

@karlvr
Copy link
Contributor Author

karlvr commented Mar 22, 2022

@rgrunber firstly just a massive thank you for the tip about the regression. I don't know why we didn't think to downgrade; I assumed it was an issue we'd introduced in our code. Our small team thanks you. Meanwhile I'll follow up on the rest, and if you haven't already, I'll try adding your notes to the Wiki.

@karlvr
Copy link
Contributor Author

karlvr commented Mar 23, 2022

@rgrunber what do you think about adding commands to this project to open the .out-jdt.ls... and .error-jdt.ls... log files? I'll tinker with it and produce a PR in case it's useful.

karlvr added a commit to karlvr/vscode-java that referenced this issue Mar 24, 2022
karlvr added a commit to karlvr/vscode-java that referenced this issue Mar 24, 2022
Resolves redhat-developer#2367

Signed-off-by: Karl von Randow <karl@xk72.com>
karlvr added a commit to karlvr/vscode-java that referenced this issue Mar 28, 2022
rgrunber pushed a commit to karlvr/vscode-java that referenced this issue Jun 21, 2022
Resolves redhat-developer#2367

Signed-off-by: Karl von Randow <karl@xk72.com>
rgrunber pushed a commit to karlvr/vscode-java that referenced this issue Jun 21, 2022
- Open log files in same view column, outside preview-mode for better
  visibility

Resolves redhat-developer#2367

Signed-off-by: Karl von Randow <karl@xk72.com>
rgrunber pushed a commit that referenced this issue Jun 21, 2022
- Open log files in same view column, outside preview-mode for better
  visibility

Resolves #2367

Signed-off-by: Karl von Randow <karl@xk72.com>
@rgrunber rgrunber added this to the End June 2022 milestone Jun 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants