[jira] Commented: (LUCENE-2611) IntelliJ IDEA setup

["Steven Rowe (JIRA)" <ji...@apache.org>]

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

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

I have tested compilation and test runs on IntelliJ IDEA 9.0.3 on Windows Vista 64-bit with Java 1.6.0_13 64-bit.

All compilation succeeds with the attached patch.

Except for the Solr module and Solr DIH contrib module test runs, each module's test run completes successfully for me.

The DIH test run works for me if I add code to TestSolrCoreProperties to clear the {{solr.solr.home}} property in {{tearDown()}} - without this code, the {{solr.solr.home}} setting leaks into the following tests and causes the resource loader to look in the wrong places.  The attached patch does not include this code, though.  When run individually, all DIH tests pass.

The Solr test run shares the {{solr.solr.home}} leakage problem with DIH test run, at least in TestContentStreamDataSource, and likely in other places as well.  However, I wasn't able to track down the causes of 500 HTTP errors and connection failures in some tests.  Maybe I didn't have my firewall set up for running these tests in IntelliJ, I'm not sure - I didn't track these issues down.

I plan on creating a similar setup for the 3.X branch.

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