[
https://issues.apache.org/jira/browse/SOLR-14759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17210281#comment-17210281
]
Dawid Weiss commented on SOLR-14759:
------------------------------------
I took a tentative look at how difficult it would be. Code-wise it's fairly
simple. I have created two branches from the current master - one with just
Lucene and one with Solr, here:
https://github.com/dweiss/lucene-solr/tree/lucene-standalone
https://github.com/dweiss/lucene-solr/tree/solr-standalone
These branches remove the counterpart project but leave much of "everything
else" in the same places. Projects compile and pass tests although full check
doesn't work because of documentation and site generation inter-dependencies
(which I will need some help with I think).
Solr fully depends on Lucene binary snapshot JARs fetched from Apache Nexus
(snapshots repo). I had to comment out 2 or 3 classes which had direct
dependencies on Lucene test classes but these can be sorted out later I think.
The question is when to move forward with this; I'm guessing it has to be done
atomically with the TLP move because of site and documentation generation?
> Separate the Lucene and Solr builds
> -----------------------------------
>
> Key: SOLR-14759
> URL: https://issues.apache.org/jira/browse/SOLR-14759
> Project: Solr
> Issue Type: Sub-task
> Components: Build
> Reporter: Jan Høydahl
> Assignee: Dawid Weiss
> Priority: Major
>
> While still in same git repo, separate the builds, so Lucene and Solr can be
> built independently.
> This is a preparation step which will make it easier to prune the new git
> repos post-split.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
