John Gibson created SOLR-4853:
---------------------------------

             Summary: SolrJettyTestBase can no longer be reused by end users
                 Key: SOLR-4853
                 URL: https://issues.apache.org/jira/browse/SOLR-4853
             Project: Solr
          Issue Type: Bug
          Components: Tests
    Affects Versions: 4.3, 4.2.1
         Environment: Java 1.7.0_21, Maven 3.0.3, OS X 10.7.5
            Reporter: John Gibson


While trying to use SolrJettyTestBase to build some unit tests for my project I 
ran into an NPE:
{code}
java.lang.NullPointerException
        at 
org.apache.solr.util.ExternalPaths.determineSourceHome(ExternalPaths.java:50)
        at org.apache.solr.util.ExternalPaths.<clinit>(ExternalPaths.java:28)
        at org.apache.solr.SolrJettyTestBase.<clinit>(SolrJettyTestBase.java:53)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:266)
        at 
com.carrotsearch.randomizedtesting.RandomizedRunner$1.run(RandomizedRunner.java:486)
{code}

Apparently some changes to SolrJettyTestBase's https support caused it to 
require the keystore that's distributed with the Solr examples.  Specifically 
the TEST_KEYSTORE static variable triggers a search for SOURCE_HOME in 
ExternalPaths which throws an NPE if the folder isn't found.

According to Steve Molloy this [used to work in Solr 
4.1|http://lucene.472066.n3.nabble.com/Test-framework-question-td4060123.html] 
and Chris Hostetter confirmed that this is a bug.  Ludovic Boutros also 
reported this [in 
SOLR-4394|https://issues.apache.org/jira/browse/SOLR-4394?focusedCommentId=13610991&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13610991].


--
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