[ 
https://issues.apache.org/jira/browse/SOLR-15455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419472#comment-17419472
 ] 

Michael Gibney commented on SOLR-15455:
---------------------------------------

Thanks for taking a look, Dawid! I agree the approach taken in this patch 
awkward, and I hope there _is_ a better way to do it. Again, my motivation for 
digging into this was that the recommendation for how to do joint development 
post-TLP-split  (with {{mavenToLocalRepo}}) didn't work without signficant 
modification. I hope to find the time to dive back into this, but I'm pretty 
sure I recall hitting issues with the composite build approach, and definitely 
recall trying to do certain things in the "normal" gradle documented way and 
finding that the Palantir plugin caused some stuff to simply not work.

I haven't yet tried the "global lucene version suffix in the main dependency 
declaration" approach, which I gather should override the dependency 
declaration in the versions.props and versions.lock files? As you say, that's a 
bit hacky too (and verbose), but not in as convoluted a way as the logic in the 
currently proposed patch.

I'm kicking myself for not documenting the dead ends I explored here. If I can 
hope for a silver lining: perhaps a fresh approach may find that they weren't 
dead ends after all?

> Facilitate joint Lucene/Solr local development workflow
> -------------------------------------------------------
>
>                 Key: SOLR-15455
>                 URL: https://issues.apache.org/jira/browse/SOLR-15455
>             Project: Solr
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: main (9.0)
>            Reporter: Michael Gibney
>            Priority: Minor
>         Attachments: solr-lucene-snapshot-build.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The recommended local development workflow for joint Lucene/Solr development 
> post-TLP split requires some changes in order to work properly. The necessary 
> changes are few, but there's also some opportunity (with minimal changes) to 
> further ease the path for developers. This issue should also encompass 
> documentation of the recommended workflow.
> Continued from a solr-dev [mailing list 
> thread|https://mail-archives.apache.org/mod_mbox/solr-dev/202106.mbox/%3ccajrvfdryqu+hbzdiimaxtsab2e4nyeais-3sfzw6v3zv3gy...@mail.gmail.com%3e].



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to