You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Tricia Jenkins (JIRA)" <ji...@apache.org> on 2013/01/22 22:56:12 UTC
[jira] [Issue Comment Deleted] (SOLR-4317) SolrTestCaseJ4: Can't
avoid "collection1" convention
[ https://issues.apache.org/jira/browse/SOLR-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tricia Jenkins updated SOLR-4317:
---------------------------------
Comment: was deleted
(was: Missing a file :()
> 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
>
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org