bq. you get a lot of entries there
That's why this is to large degree automated. You do have a lot of
entries because it's a union of all dependencies across all
sub-projects. While this may seem like a negative, it's not - it
ensures everyone stays on the same set of dependencies. Makes life
easier in the long run.
Also, you can check what depends on what by looking at the .lock file;
for example:
com.github.jnr:jffi:1.2.18 (1 constraints: b20902ab)
if you ask for this hash, you'll see where the dependency comes from
(and so on, recursively). Note that some of these dependencies are
built-time, not runtime.
O:\repos\lucene-master>gradlew why --hash=b20902ab
Starting a Gradle Daemon (subsequent builds will be faster)
> Task :why
com.github.jnr:jffi:1.2.18
org.jruby:jruby-core -> 1.2.18
O:\repos\lucene-master>gradlew why --hash=0f08b57d
> Task :why
org.jruby:jruby-core:9.2.6.0
org.jruby:jruby -> 9.2.6.0
org.jruby:jruby-stdlib:9.2.6.0
org.jruby:jruby -> 9.2.6.0
O:\repos\lucene-master>gradlew why --hash=490d7d28
> Task :why
org.jruby:jruby:9.2.6.0
org.asciidoctor:asciidoctorj -> 9.2.6.0
etc.
Dawid
On Tue, Sep 1, 2020 at 1:20 AM Erick Erickson <[email protected]> wrote:
>
> Excellent, I’ve put it in my notes… you get a lot of entries there… Thanks!
>
> > On Aug 31, 2020, at 2:59 PM, Dawid Weiss <[email protected]> wrote:
> >
> >> Is there an easy way to insure that versions.props only has necessary
> >> dependencies listed? Ideally it would be just a top-level command.
> >
> > If a dependency isn't used, check will fail. It's a feature of
> > palantir's version control plugin. The concrete task that does it is
> > named checkUnusedConstraints but you should not need to know it (or
> > care). Use check at the top level and it'll be run automatically.
> >
> >> gradlew dependencies lists pretty much everything, is it the case that if
> >> a dependency does _not_ show up in a project that it’s unused?
> >
> > That's because solr depends on pretty much everything...
> >
> > D.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
