You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if BackYourStack could support Clojure projects that use Leiningen.
The file you want to be looking at is a Clojure / EDN file (parser implemented in JavaScript), the same format as relevant for #97. A sample that should be sufficient for the purposes of BackYourStack is given on the Leiningen front page. You want to look at the list () whose first element is the symbol defproject and its elements search for the keyword :dependencies. The vector [] that follows it contains vectors [] of name / version pairs.
(defprojectleiningen.org"1.0.0":description"Generate static HTML for https://leiningen.org":dependencies [[enlive "1.0.1"]
[cheshire "4.0.0"]
[org.markdownj/markdownj "0.3.0-1.0.2b4"]]
:mainleiningen.web)
The dependencies with their descriptions, home page, source repo, versions, dependencies, licenses are usually to be found on Clojars (HTTP REST API documentation) and in some rare cases on Maven. This is the same as for #97.
The text was updated successfully, but these errors were encountered:
It would be great if BackYourStack could support Clojure projects that use Leiningen.
The file you want to be looking at is a Clojure / EDN file (parser implemented in JavaScript), the same format as relevant for #97. A sample that should be sufficient for the purposes of BackYourStack is given on the Leiningen front page. You want to look at the list
()
whose first element is the symboldefproject
and its elements search for the keyword:dependencies
. The vector[]
that follows it contains vectors[]
of name / version pairs.Sample taken from leiningen.org:
The dependencies with their descriptions, home page, source repo, versions, dependencies, licenses are usually to be found on Clojars (HTTP REST API documentation) and in some rare cases on Maven. This is the same as for #97.
The text was updated successfully, but these errors were encountered: