Has anyone ever had any conflicts between org.eclipse.jetty.websocket
and figwheel-main? So I had my front end working just fine, but I've done some work on the back end and so my deps.edn
file looks like this:
{ :deps { org.clojure/clojure {:mvn/version "1.9.0"}
org.clojure/clojurescript {:mvn/version "1.10.339"}
ring/ring-core {:mvn/version "1.7.1"}
ring/ring-jetty-adapter {:mvn/version "1.7.1"}
compojure {:mvn/version "1.6.1"}
reagent {:mvn/version "0.8.1"}
re-frame {:mvn/version "0.10.8"}}
:paths ["src" "resources"]
:aliases { :depstar
{ :extra-deps
{seancorfield/depstar {:mvn/version "0.2.4"}}}
:fig
{ :extra-deps
{ com.bhauman/figwheel-main {:mvn/version "0.1.9"}
com.bhauman/rebel-readline-cljs {:mvn/version "0.1.4"}}
:extra-paths ["target" "test" "resources"]}
:build {
:main-opts ["-m" "figwheel.main" "-b" "dev" "-r"]}}}
I get compilation errors unless I comment out the ring/ring-jetty-adapter
dependency.
Exception in thread "main" java.util.ServiceConfigurationError: org.eclipse.jetty.websocket.api.extensions.Extension: Provider org.eclipse.jetty.websocket.common.extensions.fragment.FragmentExtension could not be instantiated
at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:581)
at java.base/java.util.ServiceLoader.access$100(ServiceLoader.java:390)
at java.base/java.util.ServiceLoader$ProviderImpl.newInstance(ServiceLoader.java:803)
any ideas?