I'm getting this error:
Errors during project resolution
The following errors were found during project resolve:
Could not find artifact com.datomic:ion-dev:jar:0.9.276 in central (<https://repo1.maven.org/maven2/>)
It's supposed to be downloaded from the datomic-cloud
mvn repo, which I've defined in my deps.edn
files as:
:mvn/repos
{"datomic-cloud"
{:url "<s3://datomic-releases-1fc2183a/maven/releases>"
:why? "required by :ion-dev alias"}
}
and the alias relying on it is defined as:
:ion-dev {:extra-deps {com.datomic/ion-dev {:mvn/version "0.9.276"}}}
using the aws credentials from my default aws profile i can indeed have permission to download this artifact:
➜ nix-shell -p pkgs.awscli2 --run 'aws s3 cp <s3://datomic-releases-1fc2183a/maven/releases/com/datomic/ion-dev/0.9.276/ion-dev-0.9.276.pom> /tmp/'
download: <s3://datomic-releases-1fc2183a/maven/releases/com/datomic/ion-dev/0.9.276/ion-dev-0.9.276.pom> to ../../../../tmp/ion-dev-0.9.276.pom
(works on the .jar file too, im just testing it with the .pom, because it's smaller)
using Clojure CLI tools, the artifact is successfully downloaded:
➜ rm -rf ~/.m2/repository/com/datomic/ion-dev/
➜ clj -A:ion-dev -Sforce
Downloading: com/datomic/ion-dev/0.9.276/ion-dev-0.9.276.pom from datomic-cloud
Downloading: com/datomic/ion-dev/0.9.276/ion-dev-0.9.276.jar from datomic-cloud
Clojure 1.10.1
user=>
The problem in Cursive however persists.
I've tried the "Use tools.deps
directly" option too with tools.deps version 0.9.857
and using the CLI tools with /nix/store/g7cpwnmzfl9ikxnm7gbnq3qqgj0mynwk-clojure-1.10.1.754/bin/clojure
, but the problem persists.
The problem it causes is that all the library entries are gone from my *.iml
files, which really pollutes the list of changed files when im trying to commit, because i see 14 changed iml files.That will work for run configs, but I think onetom is talking about syncing the project to IntelliJ. That’s done in the IntelliJ process so the env vars would have to be set for the whole process I think.
That’s annoying to do depending on platform though, I’ll check to see if there’s a better solution.
Is it possible that Cursive is not using my default AWS credentials? How can we debug this?
I'm on Cursive 1.10.0-2020.3
and
IntelliJ IDEA 2020.3 (Ultimate Edition)
Build #IU-203.5981.155, built on December 1, 2020
Licensed to Tamas Herman
Subscription is active until November 27, 2021
Runtime version: 11.0.9+11-b1145.21 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 10.15.7
GC: ParNew, ConcurrentMarkSweep
Memory: 3005M
Cores: 8
Registry: ide.allow.merge.buttons=false, ide.settings.move.mouse.on.default.button=true, suppress.focus.stealing.disable.auto.request.focus=true
Non-Bundled Plugins: AceJump, IdeaVIM, Org4Idea, PlantUML integration, com.4lex4.intellij.solarized, com.alayouni.ansiHighlight, com.intellij.ideolog, com.intellij.plugins.watcher, com.paperetto.dash, de.netnexus.camelcaseplugin, io.protostuff.protostuff-jetbrains-plugin, net.vektah.codeglance, org.intellij.RegexpTester, name.kropp.intellij.makefile, org.plugin.dot.id, org.toml.lang, com.github.pshirshov.bytecodeeditor, com.intellij.plugins.html.instantEditing, com.cursiveclojure.cursive, Pythonid, org.asciidoctor.intellij.asciidoc
it is almost certain that you're not seeing the right aws creds - you can set them as env vars in your run config
I know I have definitely done exactly this before
@cfleming you might want to update https://cursive-ide.com/userguide/#download-intellij, part > Cursive will work with IntelliJ versions from the last two years, currently 2017.3, 2018.x and 2019.x. adding 2020.x as well. Question: Where can I find out whether it is safe to upgrade to latest IntelliJ (currently 2020.3), i.e. that people have tried that Cursive works just fine with it? I have been burnt before by updating to eagerly....
I'm using 2020.3 and haven't run into any blockers. But I suppose it doesn't hurt if you scroll up in this channel a bit