[
https://issues.apache.org/jira/browse/SOLR-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853849#comment-16853849
]
Erick Erickson commented on SOLR-13452:
---------------------------------------
[[email protected]] What's your sense of when this should be merged into
the main code line? From my perspective, I'm quite willing to deal with some
lack of functionality to get this into the main line code sooner rather than
later. Might bring some more folks into, you know, helping or something radical
like that.
It also seems like making this change right after a release makes sense, gives
it time to bake and we've just made a release. Waiting too long makes it likely
to wait until after the next release.
As long as I can build, precommit, and run Solr I can cope.
But no pressure ;).....
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -------------------------------------------------------------------------
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-13452
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Build
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Major
> Fix For: master (9.0)
>
>
> I took some things from the great work that Dat did in
> [https://github.com/apache/lucene-solr/tree/jira/gradle] and took the ball a
> little further.
>
> When working with gradle in sub modules directly, I recommend
> [https://github.com/dougborg/gdub]
> This gradle branch uses the following plugin for version locking, version
> configuration and version consistency across modules:
> [https://github.com/palantir/gradle-consistent-versions]
>
> https://github.com/apache/lucene-solr/tree/jira/SOLR-13452_gradle_3
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
