Unable to import Gradle build #3007

niket-goel · 2021-07-27T16:36:13Z

niket-goel
Jul 27, 2021

Hi,

I am new to Scala/Java development and want to use VIM (as I have with C for many years) for my dev work.
I have followed all instructions (multiple times) listed under https://scalameta.org/metals/docs/editors/vim/.

I cannot get the coc-metals extension to work (the Coc extensions for JAVA and python work for me).

Whenever I try to follow a symbol in a scala file I get the following error:
[coc.nvim] definition not found

While looking through the .metals/metals.log I see the following error:

2021.07.26 14:28:40 ERROR Unexpected error when compiling clients: 'error: option -source cannot be used together with --release'
2021.07.26 16:16:08 ERROR code navigation does not work for the file '/Users/***/Workspace/code/****' because the SemanticDB file '/Users/***/Workspace/code/***/.bloop/core/build/bloop-bsp-clients-classes/classes-Metals-AlHgP7w5Q1ybap7hXnD9Sg==/META-INF/semanticdb/core/***.scala.semanticdb' doesn't exist. There can be many reasons for this error.

I have removed both .bloop and .metals directories multiple times but that did not help (expected).

I am fairly new to COC and out of ideas on where to look.

One clue I have is that I am unable to find a metals-vim binary anywhere. I tried following instructions to generate the file using coursier, but I keep seeing the following errors which I am unable to resolve.

❯ ./coursier bootstrap --java-opt -Xss4m --java-opt -Xms100m --java-opt -Dmetals.client=coc.nvim org.scalameta:metals_2.12:0.7.7-SNAPSHOT -r bintray:scalacenter/releases -r sonatype:snapshots -o /usr/local/bin/metals-vim -f

Resolution error: Error downloading org.scalameta:metals_2.12:0.7.7-SNAPSHOT
  not found: /Users/****/.ivy2/local/org.scalameta/metals_2.12/0.7.7-SNAPSHOT/ivys/ivy.xml
  not found: https://repo1.maven.org/maven2/org/scalameta/metals_2.12/0.7.7-SNAPSHOT/metals_2.12-0.7.7-SNAPSHOT.pom
  forbidden: https://dl.bintray.com/scalacenter/releases/org/scalameta/metals_2.12/0.7.7-SNAPSHOT/metals_2.12-0.7.7-SNAPSHOT.pom
  not found: https://oss.sonatype.org/content/repositories/snapshots/org/scalameta/metals_2.12/0.7.7-SNAPSHOT/metals_2.12-0.7.7-SNAPSHOT.pom

Here is the output of CocInfo for me:

vim version: NVIM v0.4.4
node version: v16.3.0
coc.nvim version: 0.0.80-b427b2ccfa
coc.nvim directory: /Users/****/.local/share/nvim/plugged/coc.nvim
term: tmux
platform: darwin

Any help on this would be appreciated.

ckipp01 · 2021-07-28T18:09:21Z

ckipp01
Jul 28, 2021
Maintainer

Hey! @niket-goel. From looking at your error message:

2021.07.26 14:28:40 ERROR Unexpected error when compiling clients: 'error: option -source cannot be used together with --release'

It looks like Metals (Bloop) isn't able to compile your code. When Bloop can't compile your code, then semanticDB can't get produced, and then navigation won't work. If your project public? If not, can you share what your javac/scalac options are? It seems that -source and --release can't be used together so I'm assuming somewhere you have these both set and you can't.

Once this is taken care of, then compilation can happen, semanticDB can be produce, and you should be able to navigate.

. One clue I have is that I am unable to find a metals-vim binary anywhere. I tried following instructions to generate the file using coursier, but I keep seeing the following errors which I am unable to resolve

So coc-metals actually takes care of downloading everything for you. So there actually isn't a binary that you can locate, but it rather resolves everything and puts it together for you. So you shouldn't have to worry at all with the bootstrap script you tried. However, I have no idea where you got that one as it's trying to pull in an extremely old version of Metals.

10 replies

ckipp01 Jul 31, 2021
Maintainer

So I transfered this over to the main Metals repo @niket-goel since I'm getting the same issue with multiple clients, not just coc-metals. I'm not fully sure what's going on as I'm getting the same errors that point towards the Bloop Install process not being able to work on the Kafka repo.

2021.07.31 18:47:30 INFO  Starting build with version 3.1.0-SNAPSHOT using Gradle 7.1.1, Java 1.8 and Scala 2.13.6
2021.07.31 18:47:33 INFO
2021.07.31 18:47:33 INFO  > Task :configureBloopInstall
2021.07.31 18:47:33 INFO  > Task :connect:configureBloopInstall
2021.07.31 18:47:33 INFO  > Task :connect:bloopInstall FAILED
2021.07.31 18:47:33 INFO  > Task :bloopInstall
2021.07.31 18:47:36 INFO  > Task :clients:configureBloopInstall
2021.07.31 18:47:36 INFO  > Task :examples:configureBloopInstall
2021.07.31 18:47:36 INFO  > Task :generator:configureBloopInstall
2021.07.31 18:47:36 INFO  > Task :server-common:configureBloopInstall
2021.07.31 18:47:36 INFO  > Task :raft:configureBloopInstall
2021.07.31 18:47:37 INFO  > Task :log4j-appender:configureBloopInstall
2021.07.31 18:47:37 INFO  > Task :metadata:configureBloopInstall
2021.07.31 18:47:37 INFO  > Task :jmh-benchmarks:configureBloopInstall
2021.07.31 18:47:39 INFO  > Task :shell:configureBloopInstall
2021.07.31 18:47:39 INFO  > Task :core:configureBloopInstall
2021.07.31 18:47:39 INFO
2021.07.31 18:47:39 INFO  Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
2021.07.31 18:47:39 INFO
2021.07.31 18:47:40 ERROR
2021.07.31 18:47:40 ERROR FAILURE: Build failed with an exception.
2021.07.31 18:47:40 ERROR
2021.07.31 18:47:40 ERROR * What went wrong:
2021.07.31 18:47:40 ERROR Execution failed for task ':connect:bloopInstall'.
2021.07.31 18:47:40 ERROR > java.nio.file.FileAlreadyExistsException: /Users/ckipp/Documents/scala-workspace/kafka/.bloop
2021.07.31 18:47:39 INFO  You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
2021.07.31 18:47:40 ERROR
2021.07.31 18:47:39 INFO
2021.07.31 18:47:40 ERROR * Try:
2021.07.31 18:47:40 ERROR Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
2021.07.31 18:47:40 ERROR
2021.07.31 18:47:40 ERROR * Get more help at https://help.gradle.org
2021.07.31 18:47:40 ERROR
2021.07.31 18:47:39 INFO  See https://docs.gradle.org/7.1.1/userguide/command_line_interface.html#sec:command_line_warnings
2021.07.31 18:47:40 ERROR BUILD FAILED in 17s

Possibly one of the others might be more familiar with Gradle and know what the issue is. However, I believe the issue is on the Bloop side of things.

tgodzik Aug 2, 2021
Maintainer

Just checked newest kafka and it seems you need to first run ./gradlew compileScala and it should generate some additional classes needed in the Scala modules.

I haven't had any issues with the import itself however. You might try to replace the script path in the Metals settings to be the local directory gradlew. Just setting gradlew would probably work.

niket-goel Aug 2, 2021
Author

Thanks for the reply @tgodzik.

I am doing a full build of the project prior to running the extensions on the code every time. I tried doing the explicit scala compile and that does not help either.

Still getting the same errors in the metals.log file.

2021.08.02 08:36:13 INFO  See https://docs.gradle.org/7.1.1/userguide/command_line_interface.html#sec:command_line_warnings
2021.08.02 08:36:13 INFO  10 actionable tasks: 10 executed
2021.08.02 08:36:13 ERROR Execution failed for task ':connect:bloopInstall'.
2021.08.02 08:36:13 ERROR > java.nio.file.FileAlreadyExistsException: /Users/ngoel/Workspace/code/apache-kafka/kafka-fork/kafka/.bloop
2021.08.02 08:36:13 ERROR
2021.08.02 08:36:13 ERROR * Try:
2021.08.02 08:36:13 ERROR Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
2021.08.02 08:36:13 ERROR
2021.08.02 08:36:13 ERROR * Get more help at https://help.gradle.org
2021.08.02 08:36:13 ERROR
2021.08.02 08:36:13 ERROR BUILD FAILED in 6s
2021.08.02 08:36:13 INFO  gradle bloopInstall exit: 1
2021.08.02 08:36:13 INFO  time: ran 'gradle bloopInstall' in 6.86s
2021.08.02 08:36:13 ERROR Gradle command failed: /***/kafka/gradlew --console=plain --init-script /var/folders/vk/7_n6wxd5159bv0btnrvt07140000gq/T/metals617080777511375884/init-script.gradle bloopInstall
2021.08.02 08:36:13 INFO  Attempting to connect to the build server...
Starting the bsp launcher for bloop...
Opening a bsp server connection with 'bsp --protocol local --socket /var/folders/vk/7_n6wxd5159bv0btnrvt07140000gq/T/bsp-launcher7524435036126974221/bsp.socket'...
Waiting for the bsp connection to come up...
Waiting for the bsp connection to come up...
Waiting for the bsp connection to come up...
Waiting for the bsp connection to come up...
Waiting for the bsp connection to come up...
No server running at 127.0.0.1:8212, let's fire one...
Resolving ch.epfl.scala:bloop-frontend_2.12:1.4.8-19-4d9f966b...
Starting bloop server at 127.0.0.1:8212...
Attempting a connection to the server...
Attempting a connection to the server...
Attempting a connection to the server...
Attempting a connection to the server...
Attempting a connection to the server...
Attempting a connection to the server...
Attempting a connection to the server...
Attempting a connection to the server...
Attempting a connection to the server...
Attempting a connection to the server...
Attempting a connection to the server...
Attempting a connection to the server...
[D] Loading 1 projects from '/***/kafka/.bloop'...
[D] Loading project from '/***/kafka/.bloop/kafka.json'
[D] Missing analysis file for project 'kafka'
[D] Waiting for a connection at local:///var/folders/vk/7_n6wxd5159bv0btnrvt07140000gq/T/bsp-launcher7524435036126974221/bsp.socket...

I haven't had any issues with the import itself however. You might try to replace the script path in the Metals settings to be the local directory gradlew. Just setting gradlew would probably work.

Sorry, but I am fairly new to this ecosystem. Which settings are you sugesting here? I do not think I have tweaked metals settings yet.

tgodzik Aug 2, 2021
Maintainer

java.nio.file.FileAlreadyExistsException: /Users/ngoel/Workspace/code/apache-kafka/kafka-fork/kafka/.bloop

This is super weird, what if you remove the .bloop directory ?
@Arthurm1 Did you ever see anything like this? There should not be any issues if .bloop already exists

Sorry, but I am fairly new to this ecosystem. Which settings are you sugesting here? I do not think I have tweaked metals settings yet.

Not sure how to set LSP settings in Vim, but I am talking about metals.gradleScript setting

Arthurm1 Aug 2, 2021

@tgodzik I don't get this issue myself with Kafka and WSL2 so I suspect it's an issue with mutli-threading

@niket-goel
Try editing Kafka's kafka/gradle.properties and removing the line org.gradle.parallel=true.
Then delete the .bloop dir and re-try Metals Import Build

With parallel=true the Bloop plugin will try and import all the sub-projects at once. This greatly speeds up an import of a multi-project build but I'm not sure how well Gradle handles this when there are project inter-dependencies. Looks like we don't handle the creation of the .bloop dir - which should at least be fixable.

Arthurm1 · 2021-08-02T17:06:41Z

Arthurm1
Aug 2, 2021

It looks as though we are always setting -source and -target on bloopInstall when we shouldn't if --release is present.

As a workaround you can just remove the following from the build.gradle file...

    if (JavaVersion.current().isJava9Compatible())
      options.compilerArgs << "--release" << minJavaVersion

I'll look to fixing

0 replies

Arthurm1 · 2021-08-02T17:35:15Z

Arthurm1
Aug 2, 2021

At one point you'll have to run ./gradlew processMessages processTestMessages manually. Bloop/Metals doesn't yet have support for source code generation.

You shouldn't need to do a full build - only this.

8 replies

tgodzik Aug 3, 2021
Maintainer

Hmm.... at this point I was able to get the project compiled, do you see anything in the logs about compiling core or clients?

niket-goel Aug 3, 2021
Author

Yes.. I do see this in the metals log -

2021.08.03 10:03:32 INFO  time: Connected to build server in 0.67s
2021.08.03 10:03:32 INFO  Connected to Build server: Bloop v1.4.8-19-4d9f966b
2021.08.03 10:03:35 INFO  time: Imported build in 1.54s
2021.08.03 10:04:40 INFO  time: indexed workspace in 1m5s
2021.08.03 10:04:40 INFO  compiling ce-resource-names (5 java sources)
2021.08.03 10:04:40 INFO  compiling ce-events-api (4 java sources)
2021.08.03 10:04:42 INFO  time: compiled ce-events-api in 1.52s
2021.08.03 10:04:42 INFO  compiling clients (1447 java sources)
2021.08.03 10:04:42 INFO  time: compiled ce-resource-names in 2.15s
2021.08.03 10:04:55 INFO  time: compiled clients in 12s

tgodzik Aug 3, 2021
Maintainer

Looks like it's not trying to compile the core project, so maybe there is some additional source generated. Maybe you could try running the full compilation also?

There should be something in diagnostics causing the core not to be compiled.

niket-goel Aug 3, 2021
Author

Looks like it's not trying to compile the core project, so maybe there is some additional source generated. Maybe you could try running the full compilation also?

Did a full compile, but getting the same error in the metals log.

There should be something in diagnostics causing the core not to be compiled.

Which diagnostic are you referring to? I can check. (there is nothing that I could find so far TBH.

ckipp01 Aug 3, 2021
Maintainer

@ckipp01 -- Even with metals working fine, coc-vim is unable to provide code navigation on any scala file in the Kafka Project. Do you have any ideas on what else we can try? or is grep going to be my buddy again :)

So again the error about missing semanticDB happens when the file either hasn't been compiled and therefore wasn't able to produce semanticDB.

Which diagnostic are you referring to? I can check. (there is nothing that I could find so far TBH.

You should be able (if you're using the example mappings) do a <space> a to show all the workspace diagnostics. Do you see anything potentially causing it not to compile in there?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unable to import Gradle build #3007

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 3 comments 18 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Unable to import Gradle build #3007

niket-goel Jul 27, 2021

Replies: 3 comments · 18 replies

ckipp01 Jul 28, 2021 Maintainer

ckipp01 Jul 31, 2021 Maintainer

tgodzik Aug 2, 2021 Maintainer

niket-goel Aug 2, 2021 Author

tgodzik Aug 2, 2021 Maintainer

Arthurm1 Aug 2, 2021

Arthurm1 Aug 2, 2021

Arthurm1 Aug 2, 2021

tgodzik Aug 3, 2021 Maintainer

niket-goel Aug 3, 2021 Author

tgodzik Aug 3, 2021 Maintainer

niket-goel Aug 3, 2021 Author

ckipp01 Aug 3, 2021 Maintainer

niket-goel
Jul 27, 2021

Replies: 3 comments 18 replies

ckipp01
Jul 28, 2021
Maintainer

ckipp01 Jul 31, 2021
Maintainer

tgodzik Aug 2, 2021
Maintainer

niket-goel Aug 2, 2021
Author

tgodzik Aug 2, 2021
Maintainer

Arthurm1
Aug 2, 2021

Arthurm1
Aug 2, 2021

tgodzik Aug 3, 2021
Maintainer

niket-goel Aug 3, 2021
Author

tgodzik Aug 3, 2021
Maintainer

niket-goel Aug 3, 2021
Author

ckipp01 Aug 3, 2021
Maintainer