Skip to content

Commit

Permalink
Add disabling Gradle & Maven import to Troubleshooting doc (fixes #82) (
Browse files Browse the repository at this point in the history
#84)

* Add disabling Gradle & Maven import to Troubleshooting doc (fixes #82)

Signed-off-by: Michael Vorburger <mike@vorburger.ch>

* Update troubleshoot.md

---------

Signed-off-by: Michael Vorburger <mike@vorburger.ch>
  • Loading branch information
vorburger authored Jan 15, 2024
1 parent 267ebde commit 862f868
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions docs/troubleshoot.md
Original file line number Diff line number Diff line change
Expand Up @@ -104,6 +104,14 @@ If there is a _Build tool conflicts are detected in workspace. Which one would y

Just click _Maven_ - and this extension will still correctly kick-in and initialize classpaths and source folders etc. from Bazel.

We recommend to add the following to your repo's `.vscode/settings.json` if you run into this problem:

```json
"java.import.bazel.enabled": true,
"java.import.maven.enabled": false,
"java.import.gradle.enabled": false,
```

More background in [issue #82](https://github.com/salesforce/bazel-vscode-java/issues/82).

## Alternatives
Expand Down

0 comments on commit 862f868

Please sign in to comment.