Skip to content
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

Adding :local/root dependencies in tools-deps support errors-out if the referenced project doesn't have the same aliases #2075

Closed
awkay opened this issue Oct 27, 2018 · 0 comments
Labels
eap-only Marks issues describing bugs in EAP releases
Milestone

Comments

@awkay
Copy link

awkay commented Oct 27, 2018

I'm not sure exactly which place it is coming from. I originally had :dev and :cljs in the global settings for things to pull in by default, so perhaps it is coming from there (I can't find how to unset that globally...when I go back to it it always says it's in the context of the project); however, it is true that the project I'm using has those aliases (and I have them checked) when I try to refresh the deps.

Approximate steps to reproduce:

  1. Have some aliases checked in current project that are not in the other one.
  2. Change deps.edn to use :local/root of the project that is a dependency, but that does not share the aliases of the current project.

Should get an error.

If not, try setting the global settings to some aliases that are not in the one you're referring to.

If none of that fails, perhaps I have a cached issue?

@cursive-ide cursive-ide added this to the 1.8.0-eap9 milestone Nov 8, 2018
@cursive-ide cursive-ide added the eap-only Marks issues describing bugs in EAP releases label Sep 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
eap-only Marks issues describing bugs in EAP releases
Projects
None yet
Development

No branches or pull requests

2 participants