-
Notifications
You must be signed in to change notification settings - Fork 333
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
Fatal recursive dependency on local project #2198
Comments
After renaming |
Thanks for reporting! The issue is probably connected to the identically named modules, Bloop doesn't allow for that unfortunately and I doubt we will change it anytime soon. With the changed names this should work though. I will need to try to reproduce your issue. |
I checked out the repositories and it seems inox is not being found and compiled by Bloop. This is most likely connected to scalacenter/bloop#1002. The alternative would be to checkout inox as a submodule or use sbt BSP, which has been recently introduced. More info here: https://scalameta.org/metals/blog/2020/11/06/sbt-BSP-support.html |
I am closing this as it's not possible to fix in the current Bloop plugin, the alternative is sbt BSP, which should work without problems. |
I am faced with the same issue today. As @rjraya mentioned, renaming the respective parent and child projects so that they are not both called Then, using the Bloop server, code navigation doesn't work at all. Using the SBT sever, code navigation works only in the parent project, but not in child projects. That is, importing |
Looks like the issue is that we are unable to add the |
Youhou, indeed, that works! Thanks! 😄 |
For the record, this is what I did:
|
General context
I'm working on a project called Stainless which builds on another project called Inox. I want to be able to navigate to definitions by doing control + click on a keyword. I would like to edit Inox code after navigating to it through the Stainless code. Originally, my build.sbt file used an online version of Inox and not the local copy. So I could navigate to Inox definitions, but any changes on their code were erased after closing the files. Now I'm using another build.sbt file that will use the local copy of Inox placed in the ../ directory relative to the Stainless directory of my machine. However, the following bug is encountered:
Bug description
After loading Stainless on VSCode, I get the following error on the right lower part of the screen:
To Reproduce
Steps to reproduce the behavior:
sbt clean
andsbt universal:stage
to compile the program. Open VSCode. If needed delete the .bloop file.Expected behavior
The error itself does not prevent me from writing code in VSCode but it seems to interfere with Metals functionality. I can no longer navigate to definitions. In particular, to Inox definitions.
Screenshots
Installation:
Additional context
This is related to #768 and #1049. However, there the problem occurred while working with a dependency to be found online.
Search terms
The text was updated successfully, but these errors were encountered: