[
https://issues.apache.org/jira/browse/SOLR-15455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419765#comment-17419765
]
Michael Gibney commented on SOLR-15455:
---------------------------------------
Uwe, I think such an upgrade is already in the works (as SOLR-15538)? Not that
you're saying otherwise, but just to clarify: this issue isn't really related
to updating the standard prerelease dependency, but is about facilitating
simultaneous development across both Lucene and Solr. This issue would be
useful more in a "work-in-progress" context.
Dawid, PR #304 looks great! I look forward to trying it out. If I understand
correctly, I think the limitations you mention would not be an issue for the
kind of workflow I have in mind (fwiw). To explain a bit more:
I'd be inclined to use this for active development of features that cut across
both projects. I'd most likely develop Lucene-side features against (or merge
up to) the lucene commit that's included in Solr as the "currently active"
prerelease dependency. This approach might call for some branch-juggling, but
it'd be using git for what it's good at, and you'd have options, including:
# separately update the Solr prerelease dependency and then merge the new
prerelease merge-base into the Lucene-side feature branch.
# maintain parallel Lucene-side feature branches based respectively off of the
prerelease merge-base and lucene/main
Thanks so much for digging into this!
> 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]
