magibney commented on PR #1543:
URL: https://github.com/apache/solr/pull/1543#issuecomment-1496555628

   Purely as a convenience, for supporting dev workflows involving [Lucene 
dependency 
substitution](https://github.com/apache/solr/blob/32dd924b14ee7160cb3a47b75bbe9f51ee36a483/help/dependencies.txt#L111-L142).
   
   The workflow requires the gradle versions be the same; when they are, joint 
development is _really_ straightforward. I'm suggesting that, from my own 
perspective, if Solr were to upgrade gradle in sync with Lucene, it would make 
certain things really easy (selfish, definitely!).
   
   I don't intend to make an issue of it -- but there are lots of things that 
are treated as transitive dependencies, so to some extent it's arbitrary when 
we upgrade. What I've done to date is backport gradle upgrades to Lucene 
if/when needed, which is pretty straightforward -- worst case I can continue 
doing that.
   
   cc @dweiss, @uschindler in case they have any thoughts?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to