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 Tue, 31 Aug 2010 13:47:54 GMT

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

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

bq. Steven, I made it further and cleared up most fails. 

Cool!  Fewer failures for me on IntelliJ with this patch.  Thanks for adding sysprop clearing
to base tests.

I'm still seeing Solr network issues, likely a firewall issue.

Three Lucene TestIndexWriter tests fail because expected exceptions don't happen: testExceptionDocumentsWriter,
testExceptionOnMergeInit, and testRollbackExceptionHang.

In DIH's TestVariableResolver, two tests use the same code and fail in the same way: 
{code}Assert.assertEquals(new SimpleDateFormat("yyyy-MM-dd HH:mm").format(dmp.parseMath("/DAY")),
s);{code}
{color:red}
org.junit.ComparisonFailure: 
Expected :2010-08-31 00:00    
Actual   :2010-08-30 15:00
{color}
But when I re-run TestVariableResolver alone, all tests succeed.  I suspect there is a similar
sysprop leakage happening here, but I haven't tracked it 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: 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, 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