https://pantsbuild.org/ logo
Join Slack
Powered by
i tracked it down to a kafka dependency, but im no...
# general
p
i tracked it down to a kafka dependency, but im not sure why my managed dependencies is not overriding their value
w
were you using 
jar(…, force=True)
on the version of the annotations that you wanted?
p
no, but i thought this would force it?
Copy code
[jar-dependency-management]
default_target: 3rdparty:management
conflict_strategy: USE_MANAGED
w
maybe. i don’t fully understand how the “managed” strategy worked.
the strategy we* (credit to @adamant-mouse-92628) had used in larger repositories was to mark nearly everything 
force=True
so that any explicitly declared dependency was guaranteed to be used in favor of any implicit (transitive) dependencies
p
oh wow, good to know, thanks!
just like i always force commit to github
w
lol
that works unless some dependency has multiple explicit declarations (valid in many cases), in which case the resolver will (rightly) bail to tell you that you can’t force to both X and Y. and that is a signal to your users that they’ve got a problematic dep graph
and at that point you can either unmark 
force=…
or have the dependee change their graph.
but certainly in 2.0 the default for 
jar(.. force=?)
will be 
True
.
p
ah ok, pants 2 doesn’t have jvm yet, right?
w
not yet.
4 Views
Open in Slack
PreviousNext
Powered by