[
https://issues.apache.org/jira/browse/SOLR-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849158#comment-16849158
]
Mark Miller commented on SOLR-13452:
------------------------------------
bq. I myself use transitive deps in gradle, carefully checking for unwanted
dependencies
If i was starting my own project, this is how I would do it. I do think the
benefits outweigh the negatives and you can mitigate the negatives.
So I think we have agreement, I just don't know that a couple of us agreeing
could push it through.
But if it means we get real version resolution (that can work with
BOMs/Platforms and constraints, etc) and it's easier to add new dependencies, I
think we should def explore it. Working with the grain usually ends up nicer
than against, even if we have to add some wood or something.
> 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
> Priority: Major
>
> 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_2
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
