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
{{ message }}
This repository has been archived by the owner on Feb 24, 2023. It is now read-only.
When building an uberjar with :transitive true, parental :exclusions are lost when lifting dependencies up to the root-level.
It's worth noting that the bad library was a transitive dep of one of the source deps getting added to the uberjar. The setup looks something like:
;; source-lib/deps.edn
{:deps;; this contains `com.fasterxml/aalto-xml` which breaks `org.clojure/data.xml`
{io.netty/netty-all {:mvn/version"some-version"}}}
;; app/deps.edn
{:deps
{org.clojure/data.xml {:mvn/version"0.2.0-alpha6"}
company/source-lib {:git/url ...
:git/sha ...
;; because this is a transitive dep and `:exclusions` aren't propagated,;; `io.netty/netty-all` would be brought up as a top-level dep without;; this exclusion and re-include the bad dep.:exclusions [com.fasterxml/aalto-xml]}}}
I've just excluded netty-all as an interim fix. however, adding something like below worked for me poking around locally:
When building an uberjar with
:transitive true
, parental:exclusions
are lost when lifting dependencies up to the root-level.It's worth noting that the bad library was a transitive dep of one of the source deps getting added to the uberjar. The setup looks something like:
I've just excluded
netty-all
as an interim fix. however, adding something like below worked for me poking around locally:The text was updated successfully, but these errors were encountered: