[
https://issues.apache.org/jira/browse/SOLR-15455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419656#comment-17419656
]
Dawid Weiss commented on SOLR-15455:
------------------------------------
So, here's an experiment with the composite build approach:
https://github.com/apache/solr/pull/304
If you put a git repo checkout under lucene/main, it'll be sucked in
automatically. I tried this with the main branch (of lucene) and things seem to
work fine - I get compilation errors because of incompatible source changes (so
it seems to work!). However, when I backtrack to Lucene commit 93844d384623,
which is 9.0.0-prelease5, I get an incompatible gradle error:
{code}
>gradlew -p solr\core test --tests BasicFunctionalityTest
FAILURE: Build failed with an exception.
* Where:
Script
'C:\Work\apache\solr\main\lucene\main\gradle\validation\check-environment.gradle'
line: 44
* What went wrong:
A problem occurred evaluating script.
> Gradle 6.8.3 is required (hint: use the gradlew script): this gradle is
> Gradle 7.2
{code}
As long as gradle version is consistent, this is, I think, the best approach -
I know IntelliJ supports it in a fantastic way (no need to compile/publish
intermediate JARs, things just work), don't know about Eclipse (feel free to
try!).
Gradle incompatibility is a showstopper here - it's not about just versions but
also about incompatible build changes...
I may explore the dependency substitution a bit more but it'll have to be next
week. Unless the above is fine - it'd require bringing Solr up to speed with
lucene/main though (so that gradle versions are aligned).
> 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: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
