lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-2611) IntelliJ IDEA setup
Date Mon, 30 Aug 2010 19:14:53 GMT

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

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

{quote}
I don't think this is the same problem? This is just ensuring the class extends SolrTestCaseJ4
and doesnt have a 'nested test', there shouldn't be any others with the same problem as this
test.

Then we can separately address your solr.solr.home problem within the base classes as you
suggest, this is a separate problem I think.
{quote}

Sounds good.  Thanks for your help.

> 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: 3.1, 4.0
>            Reporter: Steven Rowe
>            Priority: Minor
>             Fix For: 3.1, 4.0
>
>         Attachments: LUCENE-2611-branch-3x.patch, LUCENE-2611.patch, LUCENE-2611.patch,
LUCENE-2611.patch, LUCENE-2611_test.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


Mime
View raw message