> Indeed, I saw that you also added spotless and tidy to the gradle build > files and provided a gradle plugin for the dependency checks. I definitely > and unintentionally talked down your work in that PR, sorry for that. >
That's fine. I'm not that happy with everything that's in the Lucene build right now. It started much simpler, then - as usual - grew tentacles all over. Solr is going to be even more challenging because of the sheer number of dependencies. But maybe I'm wrong - no other way to test this other than by trying. > So I applied most of the changes on top of mine and have almost finished > the migration. I just fail on some dependency resolution constraints that > probably need to be provided manually. I would appreciate any input on that > (I'll create a draft PR soon). > I've sent a separate e-mail about this - sorry, didn't see this thread until now. In short: I don't have any bright ideas other than what I have used in the past. I've toyed with gradle's notion of platforms but they never worked the way I wanted them to. It was probably me not understanding their concept. What I did for Lucene (custom version validation plugin + resolution constraints + not much else) is what I have been using elsewhere. I can understand what it does but I agree with you that it'd be good to improve on the documentation. Some guidelines for Lucene devs are here: https://github.com/apache/lucene/blob/main/help/dependencies.txt#L34-L82 Dawid
