lucene-dev mailing list archives

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


Mark Miller commented on SOLR-13452:

{quote}The result of this is that the buildSrc dir is treated as a separate subproject, so
all the configurations are applied to it, too.
It turns out the reason I did this was it's the only way it showed up nicely as a project
in eclipse. I'll see what I can do about getting  the buildSrc .project to somehow import
anyway - it's very nice to have that java and groovy code as a project in eclipse on import.
I guess you could import it as a separate project? What do other projects do?

> 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