[
https://issues.apache.org/jira/browse/LUCENE-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902853#action_12902853
]
Steven Rowe commented on LUCENE-2611:
-------------------------------------
bq. Can you provide any information on tests that are giving you trouble?
There is a class of problems involving "leakage" of {{solr.solr.home}} property
setting between test classes. AFAICT, Solr's resource loader uses the current
directory when that property is not set. Some tests use the current directory,
and others set {{solr.solr.home}}. When a test that expects to use the current
directory follows a test that has set {{solr.solr.home}}, things go wrong.
Adding {{System.clearProperty("solr.solr.home");}} to {{tearDown()}} in DIH's
{{TestContentStreamDataSource}} fixed the problem for me in DIH. Solr has
several tests that set {{solr.solr.home}}, e.g. {{TestSolrCoreProperties}}, and
when I added {{clearProperty()}} to {{tearDown()}} in that class, several
following tests expecting default current directory stopped failing.
There is another class of problems related to network connections, in Solr,
that I haven't tracked down yet.
> IntelliJ IDEA setup
> -------------------
>
> Key: LUCENE-2611
> URL: https://issues.apache.org/jira/browse/LUCENE-2611
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Build
> Affects Versions: 4.0
> Reporter: Steven Rowe
> Priority: Minor
> Fix For: 4.0
>
> Attachments: LUCENE-2611.patch, LUCENE-2611.patch
>
>
> Setting up Lucene/Solr in IntelliJ IDEA can be time-consuming.
> The attached patch adds a new top level directory {{dev-tools/}} with sub-dir
> {{idea/}} containing basic setup files for trunk, as well as a top-level ant
> target named "idea" that copies these files into the proper locations. This
> arrangement avoids the messiness attendant to in-place project configuration
> files directly checked into source control.
> The IDEA configuration includes modules for Lucene and Solr, each Lucene and
> Solr contrib, and each analysis module. A JUnit test run per module is
> included.
> Once {{ant idea}} has been run, the only configuration that must be performed
> manually is configuring the project-level JDK.
> If this patch is committed, Subversion svn:ignore properties should be
> added/modified to ignore the destination module files (*.iml) in each
> module's directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
