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

Erick Erickson updated SOLR-4317:
---------------------------------

    Attachment: SOLR-4317.patch

Tricia:

I revised the patch a bit to fit better in the general scheme of things, see 
below.

Does this still do what you intended? I haven't run all tests yet, just this 
one....

1> puts the test case in the "usual" place so it's run with the rest of the 
unit tests.

2> creates a temporary directory with the relevant files in it for a multicore 
setup

3> adds a solr-multi.xml file to the test files so we have one available.

This now runs either in an IDE or as a stand-alone test.
                
> SolrTestCaseJ4: Can't avoid "collection1" convention
> ----------------------------------------------------
>
>                 Key: SOLR-4317
>                 URL: https://issues.apache.org/jira/browse/SOLR-4317
>             Project: Solr
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 4.0
>            Reporter: Tricia Jenkins
>            Priority: Minor
>             Fix For: 4.2, 5.0
>
>         Attachments: SOLR-4317.patch, SOLR-4317.patch, SOLR-4317.patch
>
>
> There is still an issue after the SOLR-3826 patch was applied for 4.0 
> [https://issues.apache.org/jira/browse/SOLR-3826] in September 2012.  When 
> TestHarness is called from SolrTestCase4J the only available constructors 
> ignore coreName, set coreName = null, and initialize the default 
> 'collection1.'

--
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to