I've taken the route of extending solr, the repo checks out solr and builds
on top of that. The hard part was to figure out how to use solr test
classes and the default location for integration tests, but once there, it
is relatively easy. Google for montysolr, the repo is on github.
Roman
On Oct
mes I want to apply a patch from JIRA. I also think forking solr
will make it easier for me to contribute patches back. So here are my
questions:
*) how do I properly fork it outside of github to my own company's git
system?
*) how do I pull new changes? I think I would expect to sync new ch
Ryan,
>From a "solr-user" perspective :) I would advise against forking Solr. Some
of our consulting business is "people who forked Solr, need to upgrade, and
now have gotten themselves into hot water."
I would try, in the following order
1. Creating a plugin (sounds li
cases, and in others copying verbatim a pile of other classes.
I will send my questions to lucene-dev, thanks!
Ryan
On Friday, October 16, 2015, Doug Turnbull <
dturnb...@opensourceconnections.com> wrote:
> Ryan,
>
> From a "solr-user" perspective :) I would advise a
ggable and I end up doing an interesting workaround.
> Sometimes I want to apply a patch from JIRA. I also think forking solr
> will make it easier for me to contribute patches back. So here are my
> questions:
>
> *) how do I properly fork it outside of github to my own company's git
>
On Fri, Oct 16, 2015, at 04:00 PM, Ryan Josal wrote:
> Thanks for the feedback, forking lucene/solr is my last resort indeed.
>
> 1) It's not about creating fresh new plugins. It's about modifying
> existing ones or core solr code.
> 2) I want to submit the patch to modify core solr or lucene
