lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SOLR-3826) Allow unit test classes to specify core name during setup
Date Fri, 14 Sep 2012 18:22:09 GMT

     [ https://issues.apache.org/jira/browse/SOLR-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hoss Man resolved SOLR-3826.
----------------------------

    Resolution: Fixed

Thanks Amit!

I committed your patch along with a few more method level javadocs and fixed one more place
where TestHarness was using a "collection1" literal.

Committed revision 1384872.
Committed revision 1384877. - 4x



                
> Allow unit test classes to specify core name during setup
> ---------------------------------------------------------
>
>                 Key: SOLR-3826
>                 URL: https://issues.apache.org/jira/browse/SOLR-3826
>             Project: Solr
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 4.0-BETA
>            Reporter: Amit Nithian
>            Assignee: Hoss Man
>            Priority: Minor
>             Fix For: 4.0
>
>         Attachments: SOLR-3826_1.patch, SOLR-3826.patch
>
>
> When creating a unit test extending SolrTestCaseJ4, the corename is forced to "collection1"
which can be problematic if you want to do unit tests relying on schema/solrconfig specific
to a core. Rather than hard-coding to "collection1" allow this to be specified in the initCore
method.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message