Thinking more about it, I can solve my immediate problem by just
copy-pasting the classes I need into my own project packages (KISS
like herehttps://github.com/Filirom1/solr-test-exemple
).
I'd however suggest to refactor Solr code structure to be much more
defaults-compliant making it easier for
You've probably seen this page: http://wiki.apache.org/solr/HowToContribute,
but here it is for reference
Go ahead and open a JIRA at https://issues.apache.org/jira/browse/SOLR
(you need to create an account) and attach your changes as a patch. That
gets it into the system and folks can start
Hello,
I'm starting to write tests of my Solr integration, and have unfortunately
spent a lot of time chasing updated documentation.
Follows a test I found
herehttp://blog.synyx.de/2011/01/integration-tests-for-your-solr-config/which
uses anEmbeddedSolrServerto communicate with the server and
I use the following:
dependency
groupIdorg.apache.solr/groupId
artifactIdsolr-core/artifactId
version3.1.0/version
/dependency
dependency
groupIdorg.apache.solr/groupId
thank you. I'd like to stick to the same version (i.e. 3.2-SNAPSHOT). It
seems things have changed there.
To reproduce (should we file this and add my test as a test to avoid this
bumping up again?)
$
svn co -r 1104120
http://svn.apache.org/repos/asf/lucene/dev/branches/branch_3x/ solr
cd solr;
Hi Gabriele,
On 5/17/2011 at 9:34 AM, Gabriele Kahlout wrote:
Solr Core should declare a test dependency on Solr Test Framework.
I agree:
- Solr Core should have a test-scope dependency on Solr Test Framework.
- Solr Test Framework should have a compile-scope dependency on Solr Core.
But
On Tue, May 17, 2011 at 3:44 PM, Steven A Rowe sar...@syr.edu wrote:
Hi Gabriele,
On 5/17/2011 at 9:34 AM, Gabriele Kahlout wrote:
Solr Core should declare a test dependency on Solr Test Framework.
I agree:
- Solr Core should have a test-scope dependency on Solr Test Framework.
- Solr