Hey @seancorfield, quick deps-new / tasks question for you:
When I spin up a new project, and then I run the install task, I see this:
SLF4J(I): Connected with provider of type [org.slf4j.nop.NOPServiceProvider]
Execution error (NoSuchFileException) at sun.nio.fs.UnixException/translateToIOException (UnixException.java:92).
./target/net.clojars.test-project/test-project-0.1.0-SNAPSHOT.jar
Full report at:
/var/folders/q0/h_z9j3h90_363r9rrkcvpmp00000gn/T/clojure-8582487025730028544.edn
Error while executing task: install
Which i didn’t understand, but then learned that error was because no jar existed. That made me wonder if the install task template should have a :depends ci entry, so the jar gets built before install happens. Thoughts?I don't think the install action would be all that common in most project contexts. The lib README.md file specifically says:
> Install it locally (requires the ci task be run first):
By contrast, there is a specific ci:deploy task which does do ci + deploy
Also, the install task has this docstring: "Install the JAR locally (build via ci)."
So, no, I don't think install should have :depends [ci] 🙂
Sounds good, thanks!