You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Today Metals is having problems trying to connect to a local project.
I created a brand new Scala 2.13 project and Metals is failing to load the project. I posted below errors.
It seems it doesn't produce a bloop file. I tried using VS Code with Metals and it does work for the same project so I believe its an Emacs issue.
This started happening today.
To Reproduce
Create a brand new Scala 2.13 and try to build import. Emacs 28.1.
Expected behavior
The Metals should produce a bloop file and load the project.
Logs
2023.04.06 14:28:50 ERROR Empty build targets. Expected at least one build target identifier.
2023.04.06 14:28:50 ERROR Empty build targets. Expected at least one build target identifier.
2023.04.06 14:28:50 ERROR Empty build targets. Expected at least one build target identifier.
2023.04.06 14:28:50 ERROR Empty build targets. Expected at least one build target identifier.
2023.04.06 14:28:52 INFO time: indexed workspace in 1.37s
2023.04.06 14:28:52 WARN no build target for: /Users/shane.drafahl/test123/src/main/scala/example/Hello.scala
2023.04.06 14:28:52 WARN no build target for: /Users/shane.drafahl/test123/src/main/scala/example/Hello.scala
The text was updated successfully, but these errors were encountered:
Describe the bug
Today Metals is having problems trying to connect to a local project.
I created a brand new Scala 2.13 project and Metals is failing to load the project. I posted below errors.
It seems it doesn't produce a bloop file. I tried using VS Code with Metals and it does work for the same project so I believe its an Emacs issue.
This started happening today.
To Reproduce
Create a brand new Scala 2.13 and try to build import. Emacs 28.1.
Expected behavior
The Metals should produce a bloop file and load the project.
Logs
The text was updated successfully, but these errors were encountered: