Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Unable to specify context-specific deps in files other than ~/.clojure/deps.edn or ./deps.edn

Description

I work on a project with 160+ deps that update frequently, and are all optional so don't belong in the project's deps.edn. An alias could work here, but the deps update frequently, so I'm left updating deps.edn (home or project level) more often than I'd like to.

One solution would be to support passing a path to a file to the clj command, e.g. clj -Sdepsf "path-to-file". This way I could update that file without risking hosing my home or project deps.edn.

Environment

None

Activity

Show:

David Chelimsky January 31, 2019 at 7:24 PM

This is really a development aid. When working on, for example, aws-api, I need access to any of the available services. Today, I'll start clj with the services I care about in -Sdeps, but it would be nicer to point to a deps.edn that has all an :all-services alias in it. This is one specific example, but I think you can imagine more. And yes, I realize I could add :all-services to either of ~/.clojure/deps.edn or the one in the project, but the convenience of composing across arbitrary files in addition to implicit files + -Sdeps would be, well, convenient.

Following on the aws-api example, users have asked for a means of requiring all services. We could satisfy that need with a tools.deps-formatted variant of https://github.com/cognitect-labs/aws-api/blob/master/latest-releases.edn.

Alex Miller January 31, 2019 at 7:08 PM

What are you trying to do? Why do you have n config files?

Details

Assignee

Reporter

Fix versions

Priority

Created January 31, 2019 at 4:40 PM
Updated December 22, 2021 at 5:15 AM