Re: Checking dependencies in gradle after code is removed

2020-09-04 Thread Dawid Weiss
The location doesn't really matter I think - I just wouldn't want it to be mixed with lots of other content... These things are build-related. The same content appears when you type ./gradlew help or even just ./gradlew Try it. Dawid On Fri, Sep 4, 2020 at 5:32 PM David Smiley wrote: > Than

Re: Checking dependencies in gradle after code is removed

2020-09-04 Thread David Smiley
Thanks! This "/help" folder is something I've overlooked. You've done a fine job of maintaining a variety of information for developers. Cassandra (and everyone really): should we move /dev-docs somewhere else? A new person browsing seeing "dev-docs" might notice it first (alphabetically first

Re: Checking dependencies in gradle after code is removed

2020-09-04 Thread Dawid Weiss
> What's the path of the ".lock" file you refer to? versions.lock See help/dependencies.txt for more. D. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Checking dependencies in gradle after code is removed

2020-09-03 Thread David Smiley
Thanks Dawid for that fantastic explanation! What's the path of the ".lock" file you refer to? gradlew -p solr/solrj dependencies I observe it has many named dependency trees; some quite large. ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Tue, Se

Re: Checking dependencies in gradle after code is removed

2020-09-01 Thread Dawid Weiss
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 easi

Re: Checking dependencies in gradle after code is removed

2020-08-31 Thread Erick Erickson
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 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

Re: Checking dependencies in gradle after code is removed

2020-08-31 Thread Dawid Weiss
> 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 checkUnusedConstra

Checking dependencies in gradle after code is removed

2020-08-31 Thread Erick Erickson
Is there an easy way to insure that versions.props only has necessary dependencies listed? Ideally it would be just a top-level command. I got to wondering about this thinking about all the code that’s being removed from core and was wondering how we’d be sure that any dependencies that were re