[ 
https://issues.apache.org/jira/browse/SOLR-16553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17640174#comment-17640174
 ] 

ASF subversion and git services commented on SOLR-16553:
--------------------------------------------------------

Commit b0eff2ca815c2ec6b0487df4a77a694065c7eb43 in solr's branch 
refs/heads/branch_9x from Kevin Risden
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=b0eff2ca815 ]

SOLR-16553: solr.install.dir property not initialized


> SolrTestCaseJ4  solr.install.dir property not initialized
> ---------------------------------------------------------
>
>                 Key: SOLR-16553
>                 URL: https://issues.apache.org/jira/browse/SOLR-16553
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrJ, Tests
>    Affects Versions: 9.1
>            Reporter: Bernd Wahlen
>            Assignee: Kevin Risden
>            Priority: Minor
>             Fix For: main (10.0)
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> i tried to upgrade solr-solrj + solr-test-framework from 9.0 -> 9.1
> i have some Testcases extending SolrTestCaseJ4 and initialized like this.
> With 9.1 they fail with solr.install.dir property not initialized (i fixed 
> this adding the system property to every test class like below).
> Is this change intended? (there is no solr installation, just the test 
> framework running on temporary dir@build server).
> {code:java}
>     @BeforeClass
>     public static void beforeClass() throws Exception {       
>         System.setProperty("solr.install.dir", "./");         //inserted to 
> keep running with solrj-9.1
>         initCore("solrconfig.xml", "schema.xml", "./", "city_v2");
>         lrf.qtype = "/select";
>     }
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to