This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-01
Channels
- # aleph (2)
- # aws (23)
- # bangalore-clj (1)
- # beginners (99)
- # bristol-clojurians (1)
- # cider (3)
- # circleci (1)
- # clj-kondo (8)
- # cljdoc (4)
- # clojars (1)
- # clojure (47)
- # clojure-india (1)
- # clojure-nl (2)
- # clojure-serbia (3)
- # clojure-spec (2)
- # clojure-uk (17)
- # clojuredesign-podcast (1)
- # clojurescript (20)
- # datascript (1)
- # datomic (1)
- # emacs (1)
- # fulcro (4)
- # pathom (18)
- # ring-swagger (2)
- # shadow-cljs (31)
- # spacemacs (3)
- # tools-deps (10)
- # vscode (1)
Is there a way to express Maven plugins in deps.edn so that -Spom will include the plugin (and a repo) or do I want to do that by editing the resulting XML
use case: I want to mess with graal + javafx, specifically gluon substrate, and the recommended way to build stuff there is https://github.com/gluonhq/client-maven-plugin
Another way would be to use clojure.data.xml in a script to manipulate the generated pom afterwards
I have an issue about that. It kinda works: https://github.com/borkdude/babashka/issues/153 But it's a little hacky right now. I'm holding off until GraalVM adds proper support for javax.xml. https://github.com/oracle/graal/issues/1387
-Spom will sync into an existing pom, so just put what you want in the pom
It should stay there