[
https://issues.apache.org/jira/browse/LUCENE-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-2611:
--------------------------------
Attachment: LUCENE-2611_test_2.patch
LUCENE-2611.patch
LUCENE-2611-branch-3x.patch
These patches allow all modules' tests to pass for me under IntelliJ - as long
as no-one objects to these changes and/or finds any problems with them, I think
they're all ready to commit.
{{LUCENE-2611_test_2.patch}} changes two things (and can be applied both to
trunk and the 3.X branch):
# {{AbstractClusteringTest}} is made abstract, to stop IntelliJ from failing
because it has no test methods.
# {{TEMP_DIR.mkdirs()}} is added to {{setUp()}} in {{LuceneTestCase}} and
{{LuceneTestCaseJ4}}, so that various tests don't fail because the parent
temporary directory doesn't exist. It's important to isolate the temporary
directory used by 3.X branch tests from that used by trunk, because otherwise
3.X branch tests will fail with {{unknown index version}} errors. (The -Sun-
*Oracle* JDK's implementation of {{File.mkdirs()}} first checks for the
existence of the directory before creating its parent directories, so I don't
think this will slow Ant testing down much.)
The {{LUCENE-2611{,-branch-3x}.patch}} files differ from the previous iteration
in the following ways:
# The circular dependencies problem Erick noted are fixed:{quote}
[...] on the project settings page, there are "circular dependencies"...
1. queries, misc, common, remote
2. solr, extraction
{quote}
# All modules' test runs now use the same {{tempDir}} sysprop as the Ant tests.
# Removed the {{junit-mkdirs}} Ant pre-task for some modules' test runs,
because it was not creating the correct directories to enable using
{{build/.../test/}} for {{LuceneTestCase{,J4}.TEMP_DIR}}.
> 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-branch-3x.patch, LUCENE-2611-branch-3x.patch, LUCENE-2611.patch,
> LUCENE-2611.patch, LUCENE-2611.patch, LUCENE-2611.patch, LUCENE-2611.patch,
> LUCENE-2611_test.patch, LUCENE-2611_test.patch, LUCENE-2611_test.patch,
> LUCENE-2611_test.patch, LUCENE-2611_test_2.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
