You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2014/02/25 14:56:21 UTC

[jira] [Resolved] (SOLR-5771) Add SuppressSSL instead of static boolean in SolrTestCaseJ4

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

Robert Muir resolved SOLR-5771.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 5.0
                   4.8

> Add SuppressSSL instead of static boolean in SolrTestCaseJ4
> -----------------------------------------------------------
>
>                 Key: SOLR-5771
>                 URL: https://issues.apache.org/jira/browse/SOLR-5771
>             Project: Solr
>          Issue Type: Test
>          Components: Tests
>            Reporter: Robert Muir
>             Fix For: 4.8, 5.0
>
>         Attachments: SOLR-5771.patch
>
>
> Currently, as of 4.7, solr test-framework classes can no longer be used by downstream projects, because ssl configuration will fail (and it expects this stuff from outside the source code tree in example/ etc, which makes it impossible).
> There is a boolean to disable SSL, but it cannot work correctly unless you set it in a static initializer (to "beat" the SolrTestCaseJ4.beforeClass to the punch). Then the problem is afterClass turns it off, so if you have e.g. a base class run by 2 tests in the same jvm, boom.
> An alternative way, so people can use test-framework again, is to just have an annotation to do this. Thats how e.g. codecs and so on are disabled in lucene. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

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