lucene-dev mailing list archives

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


Uwe Schindler commented on SOLR-13452:

I'd like to stay with Groovy, too.

The main reason why most custom tasks in our Ant build were written in Groovy was also done
with "Gradle" in mind. [~mgrigorov]: most of the custom code added here (tasks like source
code checker, regenerate of unicode data, and - not yet included here - in Lucene 8.x the
MR-JAR creation with classfile patching) was copy-pasted from Ants build and just wrapped
with a "gradle task" wrapper.

> 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: []
> By default, dependencies are not transitive, but there is a special Configuration for
adding dependencies on other project internal modules that are transitive to their direct
external dependencies (their jar libs).

This message was sent by Atlassian JIRA

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

View raw message