lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (JIRA)" <>
Subject [jira] [Commented] (SOLR-13452) Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
Date Mon, 27 May 2019 06:54:01 GMT


Dawid Weiss commented on SOLR-13452:

I don't want to heat things up, but I've been wondering – perhaps instead of disabling transitive
dependencies we can just embrace them while harnessing uncontrolled dependencies via final-jar
dependency checksums (which we already do)? I am well aware of the pitfalls that come with
transitive dependencies, yet I think those final JAR checksum checks effectively prevent us
from slurping new jar files upon upgrades. And dependencies of each module become much easier
to grasp and express then. Somehow I don't think explicit flattening of all dependencies (non-transitive
expression) is much more helpful than a transitive dependency on the "root" library (possibly
excluding truly unnecessary junk), followed by sanity check preventing (or enforcing) a manual
eyeball if something changes.

> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -------------------------------------------------------------------------
>                 Key: SOLR-13452
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Build
>            Reporter: Mark Miller
>            Priority: Major
> I took some things from the great work that Dat did in []
and took the ball a little further.
> When working with gradle in sub modules directly, I recommend []
> This gradle branch uses the following plugin for version locking, version configuration
and version consistency across modules: []

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message