Gradle build server falls back to buildship when there are multiple projects #1587
Labels
bug
Something isn't working
Comments
|
Could you give a screenshot if you trigger |
How's this?
|
|
Ah, I just noticed that there is this one in your attached log That means the project is imported by Buildship instead of Build server, thus the output goes to the bin folder. What if you run |
I thought this might be the issue, since
I get the same output. |
a-ogilvie
changed the title
|
Thank you @a-ogilvie, So basically we did some change recently for the build server. The transportation is changed to use named pipe instead of stdio. That error comes from Where is your os.tmpdir()? Or, is that points to a path which is very long in character count? |
|
Do I check this in a terminal? When I run it under node in a terminal, this is the output:
That reference to Shortcuts appears because I launched VS Code using a shortcut (it just executes If I launch VS Code from a terminal instead, I get:
|
|
Will the issue disappear if you open vscode from terminal? |
|
And, did you set |
I just tried it, but the issue still recurs. I don't see the failure message in However, there is still no output in |
No, it's |
|
Is there any error logs in the server log? You can find it via command |
Here is the output. |
|
Is the project works as expected in previous version of gradle extension? |
It works as expected when using v3.15.0. Gradle for Java output: Build Server for Gradle (Log) output (this is blank for v3.16.x): |
|
Sorry, does the version you mentioned mean:
|
Yes! Sorry, mixing up packages. It works when using |
|
Ok, I can explain more about what's happening. We did some refactoring recently, those changes causes this issue.
Unfortunately, currently there is no other workaround except for using the 3.15.x One way I'm considering is to revert #1574 |
|
OK! It's good to have a diagnosis, even if there is no cure yet. For now, I'll pin at 3.15.x while you figure things out. I would appreciate it if this issue could be updated if a fix is published, but I understand that you're busy and this is OSS, so every so often I'll check if the latest version works for me and update this issue with my results. |
a-ogilvie
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Extension Name: vscode-gradle
Extension Version: 3.16.3+
OS Version: macOS Sonoma 14.6.1
VSCode version: 1.92.2
Describe the bug
When the project repository is opened in VS Code, Gradle builds the project and puts built files into the
binfolder.To Reproduce
Open VS Code with Gradle for Java enabled, and with a build folder specified that is not
bin.Expected behavior
When the project repository is opened in VS Code, Gradle builds the project and puts build files into the specified folder.
Screenshots
Output from "Gradle for Java"
Does the bug still exist if you disable all other extensions?
Yes
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: