-
Notifications
You must be signed in to change notification settings - Fork 431
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
Option to switch build tool after initial import of mixed gradle/maven project #3567
Comments
Once a selection is made, the option is stored in the workspace state database : Lines 604 to 611 in e578b50
vscode-java/src/buildFilesSelector.ts Lines 296 to 300 in e578b50
With that said, can you try what's mentioned in that comment, and just set :
in your workspace ( as a workaround ? Update: Also, yes, if https://github.com/moderneinc/rewrite-recipe-starter is the project, then I'm seeing the same error. @snjeza any idea why ? |
I guess https://github.com/microsoft/vscode-java-pack/blob/main/src/java-runtime/index.ts could be updated to modify the active build tool for the particular workspace. @testforstephen , thoughts on this improvement ? |
Pls note that Anyway, I think when you clean the language server workspace, Java extension should prompt and ask you to select the build tool again before importing mixed build tool workspace. If this is not the behavior, then it's a bug in vscode-java extension. |
|
When opening a project for the first time, the user is presented with a dialog to choose between maven or gradle when more than one build tool is present.
Correct me if I am wrong, but afterwards there is no easy way to switch to the other build tool.
Environment
Steps To Reproduce
Please attach a sample project reproducing the error
P.S Only tangentially related: The Language Support for Java Output is printing the following error when opening the project using maven:
Is that an issue with a faulty project setup for maven in the openrewrite project or perhaps an error on the language support side?
It is compiling fine with running maven and gradle from the command line and when choosing gradle as the build tool
The text was updated successfully, but these errors were encountered: