[ 
https://issues.apache.org/jira/browse/LUCENE-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902860#action_12902860
 ] 

Steven Rowe commented on LUCENE-2611:
-------------------------------------

bq. sounds like we should re-open LUCENE-2398 and fix these test problems so 
they work from Intellij?

Sounds good to me.  

BTW, unlike Ant, IntelliJ doesn't appear to support forking VM process per test 
class, so that route isn't available.

bq. Can you supply a patch with the fixes to solr.solr.home in tearDown?

Will do.

bq. Another idea would be to add your clear to 
AbstractSolrTestCase/SolrTestCaseJ4's tearDown/afterClass to prevent any 
problems? 

Yeah, I thought of that, but e.g. DIH's {{TestContentStreamDataSource}} 
directly extends {{TestCase}} - maybe it wouldn't be a problem to switch, I 
dunno - I'll look into it.

> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to